Hi everyone, I have rooted my x10 using superoneclick, I deleted the bloat wares i did not want, I flashed multitouch using flashtool, i then restored to factory and re-did all that after my wife deleted txt and dialler while playing with my new faster phone. I have the media i want, the home style and what else that i like but i want to flash a custom rom and be able to still use all my apps ect without downloading everyone of them again! I have installed xrecovery and made a backup of my current phone also. SO - I have downloaded the .rar file of the rom i would like to my computer desktop and not unzipped it and now i want to just tripple check where i save that file to on the phone. do i just save it to general sd card? do i make a new folder in sd card and put it in that? Then after i have saved it to wherever{???} do i enter xrecovery, scroll down then select install custom rom and select it from wherever? THEN {sorry i know this drags on} before i reeboot do i restore my backup to apply my apps ect or do i do that after reeboot?
ANY advice is appreciated. I know these questions sound basic to most of you but im the only person i know that even messes with this stuff none of my mates or work mates are even remotely interested so xda is my support network!
Lastly, to go back from custom rom to "normal" I assume i just run With se support and then run my backup from backup and restore app file?
model X10i
Baseband 2.0.46
Kernel 2.6.29
Build 2.0.A.0.504
Thanks everyone!!
What rom are you looking at? First, the file needs to be in zip format for XRecovery, not rar. RAR files usually are for the flash tool. Confused?
Put zip file anywhere you like on sdcard. Actually, you can download the zip file directly from your phone browser or the xda app. It will save to download folder by default. Then enter XRecovery and wipe cache, then go into advanced options and wipe battery stats and dalvik cache. After that install custom zip from sdcard.
Do NOT use xRecovery restore to restore apps and data. Use titanium backup from the market to backup and restore apps when going between android versions.
Also, why use outdated 2.0.A.0.504 firmware? Use global generic 2.1.A.0.435 firmware, it has dualtouch implementation and lots of other tweaks. Also, custom ROMs are particular about which baseband to use, so double check that. This will also get you ready for the official 2.3.3 Gingerbread update directly from PC Companion or SEUS when available.
if you have a set group of apps you would always want the fastest and best way to reinstall between versions is with an app called 'MyBackup Root' it works better with data between versions. I would also recommend Titanium Backup for just backing up and restoring all apps but MyBackup will restore them all faster for initial setup.
Sent from my X10i using XDA Premium App
agentJBM said:
What rom are you looking at? First, the file needs to be in zip format for XRecovery, not rar. RAR files usually are for the flash tool. Confused?
Put zip file anywhere you like on sdcard. Actually, you can download the zip file directly from your phone browser or the xda app. It will save to download folder by default. Then enter XRecovery and wipe cache, then go into advanced options and wipe battery stats and dalvik cache. After that install custom zip from sdcard.
Do NOT use xRecovery restore to restore apps and data. Use titanium backup from the market to backup and restore apps when going between android versions.
Also, why use outdated 2.0.A.0.504 firmware? Use global generic 2.1.A.0.435 firmware, it has dualtouch implementation and lots of other tweaks. Also, custom ROMs are particular about which baseband to use, so double check that. This will also get you ready for the official 2.3.3 Gingerbread update directly from PC Companion or SEUS when available.
Click to expand...
Click to collapse
You don't do full wipe/factory restore in xrec? You're supposed to
fiscidtox said:
You don't do full wipe/factory restore in xrec? You're supposed to
Click to expand...
Click to collapse
Never have..... and I never had any of the multitude of problems others seem to have. I go between stock 2.1, FreeX10 and WB's CM6 rom quite frequently.
Doesn't flashing a new ROM result in wiping the previous one? You don't have to factory reset before using SEUS or PC Companion...it does it within the process.
agentJBM said:
Never have..... and I never had any of the multitude of problems others seem to have. I go between stock 2.1, FreeX10 and WB's CM6 rom quite frequently.
Doesn't flashing a new ROM result in wiping the previous one? You don't have to factory reset before using SEUS or PC Companion...it does it within the process.
Click to expand...
Click to collapse
I never have problems and I always do, every instruction set I've ever read said to. If that were the case, it also wipes the dalvik and the cache partition too, so you might as well not do any of it.
Since my time with the htc hero, I've always been told to do the three (factory wipe, cache and dalvik cache).
fiscidtox said:
I never have problems and I always do, every instruction set I've ever read said to. If that were the case, it also wipes the dalvik and the cache partition too, so you might as well not do any of it.
Since my time with the htc hero, I've always been told to do the three (factory wipe, cache and dalvik cache).
Click to expand...
Click to collapse
I always thought it was cache, dalvik cache, and battery stats. I guess it might not matter as much as we think. I know that I have never had any problems restoring apps or data either, which everyone else seems to have trouble. Maybe factory wipe is causing the difficulties.
I never read anyone telling others with problems to do a factory wipe. I have only read wipe battery stats and dalvik cache.
I don't know enough to say either way, but in my experience it doesn't appear to be needed. Confused.
agentJBM said:
I always thought it was cache, dalvik cache, and battery stats. I guess it might not matter as much as we think. I know that I have never had any problems restoring apps or data either, which everyone else seems to have trouble. Maybe factory wipe is causing the difficulties.
I never read anyone telling others with problems to do a factory wipe. I have only read wipe battery stats and dalvik cache.
I don't know enough to say either way, but in my experience it doesn't appear to be needed. Confused.
Click to expand...
Click to collapse
hahaha no it definitely isn't causing any issues....
Go read any of the threads for noobs, they all say to do a factory wipe.
From every thread I've ever read, and every dev thread, the ALWAYS recommend to do a factory wipe
Here is just one example, though with search function you will literally find hundreds.
http://forum.xda-developers.com/showthread.php?t=939812
fiscidtox said:
hahaha no it definitely isn't causing any issues....
Go read any of the threads for noobs, they all say to do a factory wipe.
From every thread I've ever read, and every dev thread, the ALWAYS recommend to do a factory wipe
Here is just one example, though with search function you will literally find hundreds.
http://forum.xda-developers.com/showthread.php?t=939812
Click to expand...
Click to collapse
I didn't say that devs don't put it in their guide. I said that I always thought it was cache, dalvik cache, and battery stats.
I beg to differ about issues restoring apps and data. The devs say not to restore data (which would suck btw). I do it all the time between 2.1 and 2.2. I never had any problems with the market, angry birds etc. that others have.
Again, not saying that I know better than anyone. Just saying it is not necessary for me. I can understand the theory behind wiping everything in preparation, but I am proof that it is not required.
I also see some guides that don't say to wipe battery stats, like WB's. However, if you have battery drain that is the first thing you are told to do. Also, there are calibration apps out there that say wiping battery stats and dalvik cache are the two things needed with a new rom.
Wow what a response!
Cool, so first up i should go to the latest spec firmware {using se update service} ?
THEN, the rom i am looking at is [MOD][rendeiro2005]Cyanogen6.1.1_v02 {i now have it in zip}
It looks good from what i have read.... opinions?
So i have titanium backup as well, and ive watched videos on how to use it so ive got that sorted - as far as flashing a new firmware... some posts say you need a new kernel as well?
Sounds like my backup root is a good option, again, if i flash a whole new rom does it stay on the phone somewhere/somehow?
Hey thanks for the info guys its appreciated
If you flashed 2.0.A.0.504 global generic, then update service should work. If you flashed a regional firmware, then you should use the Flash Tool 0.2.9.1 to flash global generic 2.1.A.0.435. Then flash baseband, if needed.
Then use flash tool to root, optimize, and install xRecovery. Do a full backup with xRecovery of 2.1, so you can easily switch back to 2.1 if wanted. Also, backup with Titanium Backup or Mybackup Pro, to restore apps and data on your new rom.
Download rom custom zip to sdcard. Go into xRecovery. Wipe everything. Install custom rom zip. Using custom kernel is not mandatory, I don't think. Just need correct baseband. Restore apps and data with Titanium Backup.
i flashed the new generic no worries, re-rooted phone and installed xrecovery, used titanium backup and that worked well so all my apps and setting were as applied {including mod bootscreen} then after that i thought i should start xrecovery and load restore the backup i had made there.... it went through the process fine then said recovery finished reboot phone, so i did, and phone started to boot as normal, including with the different boot screen but then it just went to blank screen and the light at the top of the phone just shone bright white for a min or two.... then it started doing this and rebooting over and over and over.....for a half hour! so i reflashed the new generic and re-did ti backup, re-rooted and am wondering did xrecovery do that because my recovery file was made under my old firmware? or what else did i do wrong?
When going between firmwares and especially going from 2.1 to 2.2 or 2.3.
I suggest not using your back up from the previous rom.
There are compatibility issues with some apps.
When you clear your battery cache, I suggest you make sure your fully charged.
Font want your phone to think half charge is full.
You don't need to clear your cache......but you should.
It will work with out clearing the cache.
But it could fc or just go bananas.
Sent from my SE_X10i using XDA App and sliding my finger around really fast
Bootloop.... sounds like you are using wrong baseband, or you tried to reinstall xRecovery and Busybox. You don't need to worry about root, JIT, or xRecovery with custom ROMs. It's in there already...
Ive re-flashed phone with new firmware 2.1.A.0.435 Kernel is 2.6.29 Baseband is 2.1.54.
Re-rooted, re-loaded my titanium backup and phone is now as it was before i tried restoring xrecovery backup file and resulting bootloop.
now i will make a new xrecovery backup as my phone is now - All this trial and error stuff is exhausting!
Still thinking i should flash 435 Kernel?
Im happy with that so far - now i am going to try the 3g build.prop mod to see if i can get an improvement there.
Ive got speedtest but every test is so varied {from 1200 up to 420 up next test} so i don't know how well that will go.
Only after ive got a grip on all that stuff i will go for a new rom, mainly because i fly away for a weeks work in two days and wont have time to fix anything i do wrong! thanks again guys ill be donating next week to the helpful souls on here!
Restoring backup file in XRecovery is why you still have Bootloop. You just set it back to the error you had before.
Instead, do a fresh install of the custom rom zip.
You may need to flash the baseband patch if the rom isn't for baseband .54.... Flash the rom, then the baseband patch
Sorry my last post made it sound like i was back to bootloop, what i meant that after i re-flashed to standard, re-rooted ect ect without trying to restore with xrecovery my phone was back to working like it should with all my apps and multi touch ect working! so baseband is the next thing i will look at flashing....... Thanks again
Baseband 54 works for Rendero's rom.
agentJBM said:
Baseband 54 works for Rendero's rom.
Click to expand...
Click to collapse
Our use the patch with any 2.2 based rom. I'm on miui now with .55 and the patch and it works perfectly
Related
I am hoping someone has some knowledge of this...I had a lot of trouble getting CWM recovery to boot on my vibrant, but thanks to these forums, I installed ODIN, got back to Eclair, re-rooted and got CWM recovery to boot. I am using the Auxoria ROM and when I installed it I selected wipe data, etc, but when I flashed it through CWM, I am not sure if it did it or not. It appears to be working, but it seems to have a few strange behaviors from before. I then restored all apps and system data from Titanium Backup. Then got to thinking, can Titanium backup restore any system data from the Eclair ROM that would cause issues? When you restore after flashing a ROM, are you supposed to NOT install system data? I wonder if anyone has any experience with that and can make a recommendation. And Happy Mothers Day out there to any mom's out there that give so much to raise a family!
Restoring system data is absolutely a no-no
You typically can restore the green ones, if on the same os... But if you had eclair settings and restored on froyo, I bet you have a lot of little bugs.
I would odin to jfd, flash a new rom and then restore just the apps+ data.
Also, axura was great, but done master has moved to greener pastures you may want to try another. I think master said he would try and support this device still, but that's to much to ask of him I think.
s15274n said:
Restoring system data is absolutely a no-no
You typically can restore the green ones, if on the same os... But if you had eclair settings and restored on froyo, I bet you have a lot of little bugs.
I would odin to jfd, flash a new rom and then restore just the apps+ data.
Also, axura was great, but done master has moved to greener pastures you may want to try another. I think master said he would try and support this device still, but that's to much to ask of him I think.
Click to expand...
Click to collapse
Thank you....What other ROM would you recommend. I looked for one with a working GPS, and minimal bugs. I really want to do cyanogen 7 like my mytouch4g, but it doesn't seem ready yet. Am I just able to reflash and wipe data when I do? Any reason I really have to redo my odin and eclair refresh?
jman531 said:
Thank you....What other ROM would you recommend. I looked for one with a working GPS, and minimal bugs. I really want to do cyanogen 7 like my mytouch4g, but it doesn't seem ready yet. Am I just able to reflash and wipe data when I do? Any reason I really have to redo my odin and eclair refresh?
Click to expand...
Click to collapse
You can't go wrong with Trigger or the new Bionix NextGen.
I would go back to stock, just so you know you'll go to the next rom with no bugs.
Check my signature. Amazingly easy to go to jfd > new rom.
I would suggest Trigger for having everything work as it should/theming.
I went back to eclair and flashed trigger 3.2, but it seems pretty bland? No way to edit functions for home keys, or customize much of anything...looks like 2.2 really, am i missing something? I selected launcher and want to try TW launcher but I can't see where I can do that. I wanted to edit my grids but don't see that either...like replacing the app of web browser with text app...used to be able to edit on homescreen but that is even gone...
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Gutana said:
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Click to expand...
Click to collapse
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
screamworks said:
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
Click to expand...
Click to collapse
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
DirkTeur Velserbroncx said:
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
Gutana said:
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Click to expand...
Click to collapse
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
screamworks said:
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
Click to expand...
Click to collapse
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Gutana said:
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Click to expand...
Click to collapse
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
screamworks said:
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
Click to expand...
Click to collapse
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Gutana said:
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Click to expand...
Click to collapse
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
screamworks said:
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
Click to expand...
Click to collapse
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Gutana said:
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Click to expand...
Click to collapse
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
screamworks said:
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
Click to expand...
Click to collapse
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Gutana said:
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Click to expand...
Click to collapse
I only just the message 12 hours ago, if that helps?
Usually, your best bet is to go with the latest build, which you can get here. If it's stability you're looking for, go with the stable build, instead of nightlies.
Personally, out of all ROMs I've tried, I could only ever stand MIUI and CyanogenMod - but even then, MIUI started to annoy me with little things here and there. I think I'll be sticking with CyanogenMod for awhile. So, I'm not really the best authority on that. Just try some different ones, and see what appeals to you the most
What do I backup when I sbf? Can I back up everything I need with TiBu pro? When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version? How do I restore everything? Will it save app data?
Sorry for all the questions, but I need to know.
Edit: Also, if it is like getting it out of the box, what happens to my verizon plan?
Arbybear said:
What do I backup when I sbf? Can I back up everything I need with TiBu pro? When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version? How do I restore everything? Will it save app data?
Sorry for all the questions, but I need to know.
Edit: Also, if it is like getting it out of the box, what happens to my verizon plan?
Click to expand...
Click to collapse
You can back up your apps and data with TiBu. After sbf your phone will be like new, out of box, and you will need to activate your phone. It does not effect your plan. You can restore your apps and data from TiBu after the sbf.
maggard5 said:
You can back up your apps and data with TiBu. After sbf your phone will be like new, out of box, and you will need to activate your phone. It does not effect your plan. You can restore your apps and data from TiBu after the sbf.
Click to expand...
Click to collapse
Thank you. Is the only bug in 2.3.4 the battery percentage?
Arbybear said:
Thank you. Is the only bug in 2.3.4 the battery percentage?
Click to expand...
Click to collapse
I am using cm7 so not sure what issues you might encounter with stock 2.3.4.
Sent from my MB870 using XDA App
If u aren't on a rom or have any tweaks
just sbf
sbf doesn't wipe ur user data AT ALL it just upgrade ur system
BUT if u have a rom running or scripts or tweaks like that then u may bootloop after the sbf and will need to data wipe from stock recovery to remedy the bootloop
If u r dong sbf just to upgrade u wont lose ur apps data ...
ashclepdia said:
If u aren't on a rom or have any tweaks
just sbf
sbf doesn't wipe ur user data AT ALL it just upgrade ur system
BUT if u have a rom running or scripts or tweaks like that then u may bootloop after the sbf and will need to data wipe from stock recovery to remedy the bootloop
If u r dong sbf just to upgrade u wont lose ur apps data ...
Click to expand...
Click to collapse
so do you HAVE to wipe after sbf? I thought I had read on here that people had successfully sbf's without a wipe? as your post would seem to suggest?
I sbf'd for the first time in forever tonight, but didn't wipe just yet cause I didn't feel like setting everything up from scratch again.
But I still have superuser listed in my app drawer, but I seem to no longer be rooted, and had to reactivate the phone.
If the "crashed" rom is the same as the sbf no wipe needed but it's a crapshoot if "crashed" is custom rom then sbf will need wiping!
skwoodwiva said:
If the "crashed" rom is the same as the sbf no wipe needed but it's a crapshoot if "crashed" is custom rom then sbf will need wiping!
Click to expand...
Click to collapse
not necessarily
im not exactly sure why sometimes you need a wipe, and sometimes you dont.
i havent sbfd enough times to figure that out cuz i can usually just nandroid restore back to where i need to be.
but i have definitly sbfd from a rom like eclipse and NOT needed a data wipe
and i have also sbf'd when just stock rooted with some tweaks and NEEDED data wipe to stop the bootloop.
three west said:
so do you HAVE to wipe after sbf? I thought I had read on here that people had successfully sbf's without a wipe? as your post would seem to suggest?
I sbf'd for the first time in forever tonight, but didn't wipe just yet cause I didn't feel like setting everything up from scratch again.
But I still have superuser listed in my app drawer, but I seem to no longer be rooted, and had to reactivate the phone.
Click to expand...
Click to collapse
if you did a sbf you no longer have root access
i am not sure if the superuser app will be wiped away at this point if you do a data wipe either, superuser is usually a /system/app am i correct?
BUT if it is a user app(found in /data/app) then you can just uninstall the superuser via manage applications
if it is system/app you NEED root access to be able to remove the apk
if you wanna check if you are rooted or not just try to use an app that requires root access, if you are not rooted it wont work.
so yes, you inferred correctly, a data wipe is not NECESSARY after EVERY sbf flash, BUT it IS needed if you get caught up in a bootoop, data wipe from android recovery is the only way to get out of a bootloop resulting from sbf flash.
it is aso recommnded to data wipe after a sbf flash just due to issues that may arise later and u might have to data wipe then to get rid of those issues, you might end up never needing to data wipe, but if you do run into issues, that will be the solution
sorry, im not tryng to ramble here, just trying to be clear as much as i can based on my experience and based on the many results of others and their feedback.(if i have caused confusion i apologize, just ask and i will try to clear it up, i just watched hitchhikers guide to the galaxy, if u have ever read the book or seen the movie you know where my mind is right now LMAO)
well I was just going back to stock for, ya know, reasons
I had been just rooted stock at the time. I really don't want to wipe and set everything up from scratch again.
Root is gone, BSR is not functional, but they both still show in the app drawer.
Pulldown toggles are gone.
I think I'm going to give it a shot like this and see what comes
I think you will WANT to SBF>Factory Reset if you wanna do the "reasons"...
But only bug noted(that I can remember anyway) is the battery jump.
TiBu will not restore your apps or data unless you are rooted. My suggestion... do a Nandroid Backup and then do provided instructions... at least this way you can go back to what you had before hand.
SBF will bring your phone to an Out-of-Box state... Exactly how you got it at Verizon.
Questions Asked:
What do I backup when I sbf?
Whatever you want. Nandroid will be for if you want to go back to what you were using. TiBu is for if you are going to apply:
-SBF to a different Android Version.
-Apply a New Rom.
Can I back up everything I need with TiBu pro?
Depends on what you are doing. TiBu is intended for apps and app data, also keep in mind to watch what you restore because you DO NOT want to restore the Settings and other system apps when you are going to a different android version(if you know the exceptions then you know the exceptions... Dragons lie ahead if you don't know what you are doing... just trust this advice).
This WILL NOT cover user configuration in the internal settings.
When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version?
Did you upgrade or downgrade? SBF is used to go back if you brick your device or need to be on a specific android version/kernel for applying a ROM. Yes it will be out of box state with a specific android version.(i.e. If you apply 2.2 SBF you go back to 2.2 android out-of-box. If you apply 2.3.3 SBF you go back to 2.3.3 android out-of-box. etc...)
How do I restore everything? Will it save app data?
Did you Nandroid or TiBu?
Nandroid:
Apply SBF to specific android version/kernel version you were previously on(you want to be on the kernel you had with said Nandroid backup). Boot into BSR/CWM then go to restore>Internal/External Memory>Restore>Wait for application of backup>Reboot.
TiBu
Once you are on a satisfied android version/kernel open TiBu and restore whatever apps you want. You get the option to restore App(s) Only, App(s) Data Only, or App(s) and Data.
Also, if it is like getting it out of the box, what happens to my verizon plan?
Nothing!! Your Verizon Plan is saved server side and is paired with your device MEID. After a SBF is applied, you can follow the initial boot and activate your phone or dial *228 at any time to activate your device.
I hope I answered everything for you sir. Good luck with SBFing...If you have ANY bootloops or crashes after SBFing do this please:
Boot into STOCK android recovery:
1. Turn device off or Battery Pull.
2. Hold Volume Down until step 4.
3. Turn on device.
4. You should see the Moto Red Logo with white text "Fastboot" at the top of your screen. Press volume down until white text reads Android Recovery.
5. Press Volume Up to select Android Recovery.
6. You should see a Blue Android with Yellow Exclamation point.
7. Press Volume Up + Volume Down at the same time.
8. Using Volume Keys, highlight "Factory/Data Reset" then press Power Button.
9. Select Yes.
10. Reboot once complete.
Side Note:
lol I'm really bored at work right now.
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.
hey there
i hope my phone is not bricked, but i've been looking now for two hours for a solution and haven't found anything.
I have a rooted GT-9100 with jelly bean 4.1.2 XWLS8 official Samsung Rom.
In the last few days i was having problems with many apps, especially the video player and the gallery app, which wouldn't start because there wasn't enough memory (even after having deleted all the trash files and dumpstate files).
as i had not made a data wipe after updating from xwssl to xwls8 (i rooted afterwards, i didn't want to reconfigure everything again), i wanted to make a backup before i would try the data wipe now.
So i made the backup with my Rom Toolbox pro on the sd card, rebooted the phone to recovery mode, wiped the data and rebooted the phone. as always the starter mode wanted me to select the language, which i did and then suddenly the screen went black.
It started to reboot and since then the phone is hanging in the Samsung Logo.
i've tried to wipe data, wipe cache partition, wipe kalvik, no success.
tried to restore from the backup i made this morning, says md5 mismatches.
what now? any suggestions?
kind regards skapo
Sent from my girlfriend's GT-S5830 using xda app-developers app
Back to ICS stock (not 4.0.4) via Odin (Get one from Samfirmware or AndroidFirmwares.net), that will give you a clean slate & you can go from there.
Edit - Or....Search on here for the md5 mismatch thing with your backup. There's been plenty of threads on here over the past 18 mths or so. Not sure if these methods work all the time (or even at all, I've never had the problem so never had to use them), but you might as well find the threads & see if any of the suggestions for fixes work for you. Could save you doing a clean install of stock & starting again (which will obviously be somewhat time consuming).
thx for the fast reply
why ics? isn't jb stable enough?
is there actually a pure rom like the nexus phone for the s2? i was wondering if the touchwiz from samsung might be responsible for so many problems...
Sent from my GT-S5830 using xda app-developers app
Worry about all that once you get the phone working normally again, this should be the only thing you're thinking about right now. First thing's first
yeah, you're right. i'll give it a shot i'll update this post tonight. thx
UPDATE:
Ok, i've reinstalled a ICS 4.0.3 I9100XXLPS, Buildnumber IML74K.XWLP7 (whatever this may be, where is the guide to the structure of Android and all the definitions, can't find any proper introduction).
It seems to work fine, but i had to wipe data and wipe cache partition, otherwise the phone still got stuck in the boot loop.
So what now? I've tested the root access, which of course isn't available anymore after flashing the ICS Stock ROM.
Do i need to install first a JB ROM with root access to (try to) restore from my backup or can i do it right from here rooting the ICS ROM?
Almost Solved
sKapo_daVinci said:
yeah, you're right. i'll give it a shot i'll update this post tonight. thx
UPDATE:
Ok, i've reinstalled a ICS 4.0.3 I9100XXLPS, Buildnumber IML74K.XWLP7 (whatever this may be, where is the guide to the structure of Android and all the definitions, can't find any proper introduction).
It seems to work fine, but i had to wipe data and wipe cache partition, otherwise the phone still got stuck in the boot loop.
So what now? I've tested the root access, which of course isn't available anymore after flashing the ICS Stock ROM.
Do i need to install a JB ROM first with root access to (try to) restore from my backup or can i do it right from here rooting the ICS ROM?
Click to expand...
Click to collapse
OK, i think i've got the problem solved:
The first thing i tried is to root the ICS and restore with the CWM. Interesting that this time it didn't give me any md5 mismatch, but it suddenly stopped during the process and the phone booted normally to ICS, in other words the restore didn't work.
So I downloaded the latest SGS2 JB I9100XWLSJ again (i had that one installed before the whole mess), i thought that the one i had installed before may have been corrupted. I flashed the ROM, wiped data, cache and dalvik cache and rooted the phone with Siyah. From there i tried to restore again, but again it stopped because of the md5 mismatch.
At least the new JB ROM booted successfully, which allowed me to access the backup file in the phone's internal sd with my PC.
I edited the nandroid.md5-file with notepad ++ and the md5 calculator. There's a good instruction from here. The folder distribution from the original instruction is a little bit confusing, that's why i've uploaded another one
I recalculated every md5 number for each file in the backup (except the nandroid.md5-file itseld of course and in some cases the .android_secure.img [i didn't have such a file]) and modified the md5 numbers inside the nandroid.md5-file.
That solved my problem :laugh: I was able to restore from my backup .
Even so, the video player app is still crashing. I restored my files and all the config, but with it the same problems i had before :crying:
Good work on finding a solution & posting it here, I'm sure it will help someone at some point in the future
Re: the FC's with the video player (which one ?), sounds like restoring it/it's settings is causing you problems. You might want to try clearing data on it first - go into settings/apps/all & select the app, then clear data; and if that doesn't work, uninstall it then do a clean install without restoring the app or settings. If the settings were backed up on ICS & you're currently using JB, that may be the cause of the FC's.
sKapo_daVinci said:
I edited the nandroid.md5-file with notepad ++ and the md5 calculator. There's a good instruction from here.
Click to expand...
Click to collapse
Thank you so much for bringing that thread to my notice! Could be useful in the future..:thumbup:
And good work solving it on ur own. XDA needs more guys like u!
If u do manage to solve all ur issues, please add [SOLVED] to the title of ur post, so that others too may benefit from ur solution.
"To err is human, to forgive is divine"
Sent from my SGS II