Related
Hello,
I'm trying to Restore one of my backups from recovery and after reboot, the phone stuck on the white HTC screen, It happen to all the backups I have.
It's the first time this is happen, I managed to do that before without problems.
My recovery version is 3.0.1.5 and always has been (I didn't upgrade/downgrade) it ever.
I'm able to install a new fresh ROM, but I'm not able to Recover and this is very important for me.
I read other threads about it but neither are solving my issue.
Please advice.
Thanks!!!
(The backups are Coredroid and RCMixHD both Gingerbread).
I had the same problem and solved it by first flashing the old, clean ROM (in my case RCMix) and after the first successful boot restoring only data and system (in CWM "backup and restore" -> "advanced restore"). And I suppose if you restore system, the backup should be the same ROM as the one you have installed.
After that everything worked fine again...something must be wrong with CWM, seriously...
frosty_ice said:
I had the same problem and solved it by first flashing the old, clean ROM (in my case RCMix) and after the first successful boot restoring only data and system (in CWM "backup and restore" -> "advanced restore"). And I suppose if you restore system, the backup should be the same ROM as the one you have installed.
After that everything worked fine again...something must be wrong with CWM, seriously...
Click to expand...
Click to collapse
yes, but from then, are you able to do Restore as regular, like you did before without any problems ?
Or that only your system is working but your'e still unable to do restores ?
Well I am unable to do a complete restore, but it works when I first install the ROM and afterwards manually restore system and data. So I have got everything set up as if I did a normal restore.
It's almost the same as a regular restore any way, you won't notice any difference.
I will take a look into the CWM backups, maybe I'll find the reason for this bug.
thanks, that's nice, it's not so comfortable, but if I wont have a choice I will do that.
In the meanwhile I prefer fixing this issue, anything can do to fix it ?
(Strange, but my problem has been started since I'm using RCMix, may something in this ROM conflicts with CWM?!)
Quite the same here, I'm using RCMix too. But it might just be a random correlation, unless more people have this problem.
Until it is fixed I will just use my workaround, it is not too much trouble luckily
Oh yeah and I took a look in my backups. On the surface everything seems to be in order....
frosty_ice said:
Quite the same here, I'm using RCMix too. But it might just be a random correlation, unless more people have this problem.
Until it is fixed I will just use my workaround, it is not too much trouble luckily
Oh yeah and I took a look in my backups. On the surface everything seems to be in order....
Click to expand...
Click to collapse
I'm using CM7 and have no problem restoring my Nandroid backup, so IMHO it may be a specific issue with RCMix
Ok guys, problem has been solved by installing the latest recovery version from Rom Manager app. Then restart, wipe and... Restore successfully.
I still suspect the RCMixHD, because the problem has been started since I have installed it, maybe it changed something in the CWM, I'm afraid to reinstall it now , I'm sticking with Coredroid 5.3
So yea...as much as I know my desire's motherboard needs replacement...And I dont have warranty. Is there any way to fix it without changeing whole motherboard?
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
There's something called insurance.
Swyped...
hypophysis said:
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
Click to expand...
Click to collapse
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
LordRyver said:
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
Click to expand...
Click to collapse
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
MonacoHias said:
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
Click to expand...
Click to collapse
1. I had,but it used to turn off and get into boot loop while playing games like GRave defense. Never happened while playing shoot bubbules.
2. DevNull. First was dev,then leedroid,now back to dev. I keep him in sd card in case my phone wont turn on. Sometimes it restarts in middle of movie so I left him 2 times until morning and it first time turned on and second time didnt,again started to restart. Same with reflashing roms. Sometimes helps,sometimes no.
3.Yes.Radio_32.56.00.32U_5.17.05.08
4.Yes. I had hboot 0.83 or 0.93 and I used AlpharevX and then unrevoked.
5.Yes.
6.I dont know, I got it when I bought phone. (it was used when I bought it.)
7.Hm......Well...I dont think so...when I bought it, I turned phone off and after um... about 1 h I tryed turn it on and it started restarting. Then after some time turened on again.
And btw now it sometimes starts restarting not even hot.
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
mortenmhp said:
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
Click to expand...
Click to collapse
But that used to happened with original rom too...un...one guy said that bootloop is because motherboard is faulty. Now I just watched whole movie. And it was ok. But I tink if I would use market or opera it would restart. But im not sure. Sometimes it dosnt restart. And if I would flash all correct software my phone would turn on quicker?
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
mortenmhp said:
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
Click to expand...
Click to collapse
Sorry. By bootloop I mean my phone restarts and then just starts viberating and just stays in white htc logo screen. But after some time I can enter android system. This happanes when I do something with my phone.
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Did that already...first time all was the same,but now looks kinnda better. If it wont go to restarting screen while chagring i'll be happy...After doing factory reset it started to move things from pc to sd very slowly.
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Well now it runs rll great And I didn't do anything different. It restarted while charging but at about 98% it was cold again and I succesufly turened it on with first try. If something will go wrong i'll try do 777ace guide. Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Also if there is bad app,could I try downloading it again after restoring with titanium?
LordRyver said:
Also if there is bad app,could I try downloading it again after restoring with titanium?
Click to expand...
Click to collapse
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
LordRyver said:
...
Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
Click to expand...
Click to collapse
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
MonacoHias said:
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
Click to expand...
Click to collapse
Windows. Yes. It gets overheat. And switching to another USB port didn't helped. But I noticed that usb cable's part that puts into pc was a bit hot.
MonacoHias said:
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
Click to expand...
Click to collapse
hm...I think problems start when I install classic ghost radar
Ok...can some1 explain me. my phone started to restart while moving movie from pc to sd. Now it's cold. But when I turn it on, it loads and after 1 sec in android system it starts restarting again. why?
HI all,
I've flashed CWM5.5 from the recomended thread and installed Cyanogen 9 Alpha 1. Unfortunatly the phone seems to boot up but does never leave the boot animation screen (yes I've also flashed gapps after cyanogen).
Anyone can identify this pattern? On a normal device I could hook it up through a serial cable and try to debug the boot... Eventually how can I do that with a I8150?
Well, any help would be most welcome. I'm totally available for testing and I do have some experience with Linux even at a very low level/system space.
Install
Use CWM5.
Warning: Only use this recovery to flash CM9. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM9 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
read it thoroughly ...
1st you must flash update*.zip
2nd gapps*.zip
that just about it ....
what is your current kernel ?
That was pretty much it... I've restored not the original operator crap ROM, but instead the Value Pack ROM.
CyanogenMod9 seemed to install ok, but just looped and the phone didn't finished the boot. I'm not really sure on what happened. I'm just finishing restoring the stuff
I'm guessing you didn't wipe data/cache.
I did a factory reset, but sure, it might not have wiped the whole thing... Going to try again.
@argo68
True mate, the issue was not wiping the user cache. I've wiped the cache now from ClockWorkMod and it worked ok. Takes some time to boot compared to the stock samsung ROMs but it works fine
Anything you need tested ? I can most likely help.
I do have a problem with apps though, for example, GMAIL doesn't show the body of the message... as you can see on the screenshot, but I guess this is a app related issue maybe?
http://susepaste.org/images/39081870.png
After a reboot somehow it boots a bit faster and the gmail app is now displaying the body of the email and it seems a bit faster...
Good work, gonna ride this for a few days and see what happens.
@argo68
If you need beta testers, let me know. I'm off work this days but can't wait to get into my lab and check this stuff deeper
@argo68
he is arco68
just in case he takes offence, which I don't believe he would
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
ketheriel said:
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
Click to expand...
Click to collapse
reAdy for some BEAR ????
do you actually mean bear or beer ??
chocolemon said:
reAdy for some BEAR ????
do you actually mean bear or beer ??
Click to expand...
Click to collapse
Maybe it's the Nordic ascendance. They fight a bear with one hand while holding the beer with the other.
Hi I'm using this cyanogen mod for quite a few days now. The back side of the phone is always warm and the battery is drained very fast. Anyone have this similar problem?
I'm sure that I install the ROM correctly as i cleared everything on the phone with CWM 5.0.0.4 before and after. (Phone data / Cache Partition / Dalvik Cache / Battery Cache)
Any help would be appretiated
No such problem here. You should use an app to check what frequency the phone is running at in idle, and also how much load there is on the cpu.
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?
Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.
As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.
CAUTION: This method of data recovery will work under a wide variety of situations; however, you must consider the following:
1) When going from a stock or stock-based ROM to another stock or stock-based ROM, this method should work very well. It doesn’t matter if it’s the same ROM as long as both are based on a stock ROM.
2) When going from a stock or stock-based ROM to an AOSP-based ROM, such as CM or AOKP, this method may/will not work. Similarly, when going from an AOSP-based ROM to a stock or stock-based ROM, this method may/will not work.
Use common sense, and always follow instructions provided by the ROM Developer.
This method also removes any concern as to whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.
Here we go …
1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT
If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.
Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.
Okay, you can hit the thanks button now.
Peter
(formerly PeterHTC)
PeterGuru said:
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?
Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.
As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.
This method works “perfectly” if you’re upgrading an existing ROM. However, I can’t see any reason why it wouldn’t work equally well even if you’re coming from another ROM. Either way, use common sense, and always follow instructions provided by the ROM Developer.
This method also removes any concern whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.
Here we go …
1.Boot into Recovery
2.Make a Nandroid backup
3.Wipe data/factory reset
4.Wipe cache partition
5.Wipe Dalvik Cache
6.Flash ROM
7.DO NOT REBOOT – STAY IN RECOVERY
8.Select backup and restore
9.Select advanced restore
10.Select the Nandroid backup you made above
11.Select Restore data
12.Select Yes – Restore data
13.WAIT!
14.REBOOT
If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.
Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.
Okay, you can hit the thanks button now.
Peter
(formerly PeterHTC)
Click to expand...
Click to collapse
Good to see you here from the one x. I'm glad to be back on Sammy. One x just had too many bugs for me and no memory card was a deal breaker.
This tutorial seems legit, I'm just concerned that doing this could overwrite mods the rom developer implements and cause issues. Any response to that concern?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Usually use Titanium Backup myself, so I can selectively select which apps to restore with data. If you're going from a stock based ROM( stock modified ) to AOSP ( CM, AOKP, or any of their kangs ) then I don't think I'd recommend this shotgun method of restoring. However Stock -> Stock this is very fast and shouldn't cause any issues.
About mods, not sure, most mods are going to be in /system so those should be fine, however anything themed will be overwritten I believe. ( CWM wipes and restores, not an additive restore correct? )
I completely agree ...
RubenRybnik said:
Usually use Titanium Backup myself, so I can selectively select which apps to restore with data. If you're going from a stock based ROM( stock modified ) to AOSP ( CM, AOKP, or any of their kangs ) then I don't think I'd recommend this shotgun method of restoring. However Stock -> Stock this is very fast and shouldn't cause any issues.
Click to expand...
Click to collapse
Yes, Titanium has the advantage of allowing you to selectively restore apps, etc.
RubenRybnik said:
About mods, not sure, most mods are going to be in /system so those should be fine, however anything themed will be overwritten I believe. ( CWM wipes and restores, not an additive restore correct? )
Click to expand...
Click to collapse
I completely agree. If you're sticking with a stock-based ROM, or up-dating almost ANY existing ROM, then this method should work just fine; however, like you said, I would not recommend it if going from stock to AOSP, or vice versa.
I would also agree concerning the mods, which are almost always in /system, and aren't the theme files anywhere BUT in the data folder? Please correct me if I'm wrong.
Peter
Same here ...
lessthanzach said:
Good to see you here from the one x. I'm glad to be back on Sammy. One x just had too many bugs for me and no memory card was a deal breaker.
This tutorial seems legit, I'm just concerned that doing this could overwrite mods the rom developer implements and cause issues. Any response to that concern?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I would have to agree. I had far too many little glitches with my ONE X and ONE XL that were just too annoying. So far I could not be happier with the S3.
Peter
Good tip, Peter. I never knew about that one and it will come in handy for me!
Am I the only one who also formats /system in Recovery?
thank you for this! im jumping from stock to diet ics and this tip helped a lot.
im also coming from about a months use of HTC One X. its only been one day with this sg3 and i already prefer it over the htc one x.
Is ROM Manager still advisable or did Koush move on and it is an abandoned project like some of the reviews suggest in the Google Play store? I used to use this to flash and manage my NANDROID's and it was super easy.
P8TRIOT said:
Is ROM Manager still advisable or did Koush move on and it is an abandoned project like some of the reviews suggest in the Google Play store? I used to use this to flash and manage my NANDROID's and it was super easy.
Click to expand...
Click to collapse
I just used his Rom manager to flash the AT&T recovery and it works great.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
PeterGuru said:
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?
Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.
As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.
This method works “perfectly” if you’re upgrading an existing ROM. However, I can’t see any reason why it wouldn’t work equally well even if you’re coming from another ROM. Either way, use common sense, and always follow instructions provided by the ROM Developer.
This method also removes any concern whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.
Here we go …
1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT
If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.
Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.
Okay, you can hit the thanks button now.
Peter
(formerly PeterHTC)
Click to expand...
Click to collapse
When I had my old Droid X2 (MB870), this is the method I used all the time, and it was very simple and straightforward, if I am understanding you correctly, this method is conditional in that you have to be coming from an existing flashed ROM? So for instance I just rooted yesterday through Odin but am still on stock, this method wouldn't work for me? It would be awesome if this could be utilized universally for what ever (rooted state), is this in fact the case or what exactly is the specific condition if any?
I will be adding a cautionary note to the first post ...
P8TRIOT said:
When I had my old Droid X2 (MB870), this is the method I used all the time, and it was very simple and straightforward, if I am understanding you correctly, this method is conditional in that you have to be coming from an existing flashed ROM? So for instance I just rooted yesterday through Odin but am still on stock, this method wouldn't work for me? It would be awesome if this could be utilized universally for what ever (rooted state), is this in fact the case or what exactly is the specific condition if any?
Click to expand...
Click to collapse
Although this will work under many different circumstances, there are a few very important restrictions, which I will add to the first post in a few minutes.
Peter
Not to with this but there is a software update be AT&T if installed will it take away root?
Sent from my SAMSUNG-SGH-I747 using xda premium
Carrier up-dates may be disabled ...
dahlem said:
Not to with this but there is a software update be AT&T if installed will it take away root?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Although I would like someone to confirm this, it is my belief that, if you root your device, then software up-dates from the carrier no longer work.
Peter
This works fine with ApOcAlYpSe 7_10_12 ROM
This method I can confirm works perfectly with the ApOcAlYpSe 7_10_12 ROM by smartguy044. I installed the Rom and restored everything from a previous stock setup that I did a nandroid of right before flashing. From start to finish the whole process took me less than the 10min as advertised. Just thought I would share just in case anyone was on the fence or concerned about using this with the ApOcAlYpSe 7_10_12 ROM.
Thank you for the confirmation ...
hkeyman said:
This method I can confirm works perfectly with the ApOcAlYpSe 7_10_12 ROM by smartguy044. I installed the Rom and restored everything from a previous stock setup that I did a nandroid of right before flashing. From start to finish the whole process took me less than the 10min as advertised. Just thought I would share just in case anyone was on the fence or concerned about using this with the ApOcAlYpSe 7_10_12 ROM.
Click to expand...
Click to collapse
Thank you for the confirmation.
I hope this helps those who are afraid to flash new ROMs because the entire process (from Nandroid to installing all apps and re-establishing settings), can take hours. I never really trusted Titanium, even though many do, so before hearing about this method, it would take me anywhere from 2-6 hours to get my device back to exactly how I want it, with all settings re-established. Flashing and installing apps wasn't the issue, which took me less than an hour. It's opening every single app and adjusting the settings that often took hours.
Peter
You really don't have to worry about restoring data if you flash a ROM that doesn't format the data partition. I have found that some/most don't wipe data. So you can just flash the ROM and reboot and go on your way. Of course do make a backup just in case.
I use TiBu 100% of the time. Never had it not work.
wgarrido said:
You really don't have to worry about restoring data if you flash a ROM that doesn't format the data partition. I have found that some/most don't wipe data. So you can just flash the ROM and reboot and go on your way. Of course do make a backup just in case.
I use TiBu 100% of the time. Never had it not work.
Click to expand...
Click to collapse
You are correct in your suggestion "If" the Rom installed does not wipe or format the data. This is obviously a alternate, fast method for restoration of user data if needed in a pinch or just as a normal way of getting your configuration and apps back to the way you had them configured previously (either stock or on another similar installed ROM).
I am not sure what you meant by you use TiBu and not have it work? When restoring from TiBu you should always just restore missings Apps with Data and avoid anything System related as it would most likely overwrite anything that a ROM customization may have just installed and will cause issues whether minor or even serious. I would suggest only messing with system restore items if you absolutely know what you are doing. That aside I agree with Peter as TiBu as good as a backup as it is, its time consuming...but its another precautionary backup method needed as a just in case.
hkeyman said:
You are correct in your suggestion "If" the Rom installed does not wipe or format the data. This is obviously a alternate, fast method for restoration of user data if needed in a pinch or just as a normal way of getting your configuration and apps back to the way you had them configured previously (either stock or on another similar installed ROM).
I am not sure what you meant by you use TiBu and not have it work? When restoring from TiBu you should always just restore missings Apps with Data and avoid anything System related as it would most likely overwrite anything that a ROM customization may have just installed and will cause issues whether minor or even serious. I would suggest only messing with system restore items if you absolutely know what you are doing. That aside I agree with Peter as TiBu as good as a backup as it is, its time consuming...but its another precautionary backup method needed as a just in case.
Click to expand...
Click to collapse
I was just saying that TiBu hasn't lost data or anything. I know about restoring system data. I have gotten away with restoring some of it in the past.
PeterGuru said:
Although I would like someone to confirm this, it is my belief that, if you root your device, then software up-dates from the carrier no longer work.
Peter
Click to expand...
Click to collapse
OTA's should work with root as long as you are on stock and haven't altered your build.prop. On that note, I haven't heard anything about a Rogers update?
I haven't heard anything from Rogers, either ...
David Dee said:
OTA's should work with root as long as you are on stock and haven't altered your build.prop. On that note, I haven't heard anything about a Rogers update?
Click to expand...
Click to collapse
I haven't heard anything from Rogers regarding an up-date, either.
And thank you for answering the OTA question.
Peter
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Anthonyl123 said:
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Switch ROMs.
Maybe your phone just doesn't play nice with the Hyperdrive ROM. Try out a new one, or do a clean install of it and see if that fixes it!
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Mr._Happy said:
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Click to expand...
Click to collapse
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
topherk said:
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
Click to expand...
Click to collapse
Ive done options 1 and 2 but here is what I have installed on my phone
When I ran the aroma installer I chose the option to run a full installation with the devs choice of mods and stuff etc. So I have the tw launcher installed along with the multiwindow mod and pretty much everything else.
Sent from my SPH-L710 using xda app-developers app