Hi all,
Just thought I would try the MIUI rom on my phone. I completed a backup through nandroid and flashed the new ROM.
Tried it for a bit and wanted to go back to my original setup. Rebooted into clockwork, fact reset the device (format data/cache everything) and completed the restore (which said it worked correctly).
Now every time I turn on the phone I got the HTC on a white background and it goes no further.
Any help would be appreciated.
Thanks.
Should also mention that I'm using version 3.0.2.6 of ClockworkMod
Hi
I recently got an OTA update notification on my Defy+ but it does not work. It is an upgrade from 2.3.4 to 2.3.5.
I am currently on this Stock ROM
4.5.1-134_DFP-74
It is rooted, 2ndInit and the only MOD is the 720p Video upgrade.
As the OTA didn't work I decided to flash a whole new SBF and chose this one
4.5.1-134-DFP-125 - CEE
I flashed it and it all went more or less okay (some slight issues with boot loops but sorted now). I also took a Nandroid backup of my 2.3.4 set up (on first flash I re flashed the Nandroid just to make sure it worked and it did).
I initially flashed the 2.3.5 SBF and then ran a Titanium Backup of all my apps and data. However, I found when I checked the ROM it was showing the 2.3.4. I realised that TB must have been flashing over all the 2.3.5 files like flashing the Nandroid back up does.
This morning I re flashed the 2.3.5 SBF and set my phone up without the TB initially and it showed as the 2.3.5 ROM in settings. After installing all my Apps from Market I used TB to install data only on some apps where I wanted to save time setting them. All were download apps (Handcent, eBay etc). The only system app I did this on was Blur Accounts.
I then checked my ROM version and it is showing it as my original Stock ROM!! I can't understand how restoring some data on some apps would do this.
Before I re flash the 2.3.5 SBF and manually install the phone can someone explain what is actually going on here please? I am assuming that by restoring some of the Titanium Backups I have set it back to the 2.3.4 ROM.
I should add the phone runs fine (if anything it is much smoother than before but that is probably due to me running script manager).
Thanks in advance for any advice.
Regards
Bump...any ideas?
Has anyone else had bad experiences with CWM Touch? I started to use it in place of TWRP since it would work with Rom Manager (which is still kind of useless compared to what it was on the OG Droid) but it has screwed me over twice. The first time was I was switching ROMs so I made a backup and when I went to restore it later it said MD5 sum mismatch so I was pretty much screwed. Just now I went to try and make another backup since I had just installed Paranoid Android and had everything setup and I wanted a backup before I flashed Clemsyn's elite kernel. Knowing that I didn't have much space left I selected clean nandroid space assuming it would get rid of the previous backups, after it finished it said it was done but never brought back the UI so I had to do a hard reboot.
Upon boot up it just hung at the Google screen, I did a few more reboots and got the same thing. I went into the bootloader via the three finger method (which to my surprise worked without connecting to a USB port, so I'm assuming this is a problem with the 3rd party recoveries and not the device itself?) and selected recovery but i was stuck at the Google screen again.
Time to switch back to TWRP!
TL;DR CWM Bricked my Nexus and the backups don't work
Hello, I rooted my handset yesterday following the tutorial on Android Forums, my Vodafone (UK) branded build is JDQ39.I9505XXUBMEA
I also installed CWM PhilZ Touch 5 (v6.0.3.7)
It works fine inside the OS but occasionally, when I restart the phone, it just hangs on the Samsung Mobile logo?
When that happens, I have to hold the power button then hold Up+Home and boot into PhilZ and then go to Reboot System Now and that restarts the phone mostly back into Android as normal.
Any ideas what the problem could be?
Good question. Haven't come accross something like that. I suggest flashing whatever ROM you want. It should get rid of your problem. If you still want a stable rom with all Samsung features, download Wanamlite 2.0 rom. It's a very good replacement for your stock rom. Or you can try Omege rom. It includes all samsung bloatware incl. S HEALTH etc.
Good luck and let us know! :thumbup:
Thanks for the quick reply.
I have used CWM to do a full data back up onto my SD card. As I'm new to rooting, is there a way I can restore that data onto a new rom so I don't have to keep setting up my phone completely? Even like, settings and shortcuts on the home screen etc?
Not really. What you can do is backup all your apps etsc with Titaniumbackup. With this you can restore all apps+data.
Setting up your phone isn't that bad considering its only settings.
Tha initial backup youve made through CWM is only a backup of your system. I dont think this includes all apps. I never revert to a previous rom. I prever a clean install to have the best rom exlerience without bugs etc.
If you try a new rom. And you dont like it at all(not likely) or for whatever reason you want to revert to you stock rom. You can restore it via CWM. Thats about the only reason why youve made that backup.
Good luck.
Oh yes, one more thing. Remember to press the Thanks button :thumbup:
Will that (Titanium) back up my apps exact settings as well? Say like my login details or custom settings I have changed within an app?
So the back up I made using CWM (which was complete data and apps and cache I think?) can restore my phone to exactly the instance when I pressed back up including the ROM?
To be honest, I'd be interested in the same Vodafone rom that's rooted so I can just use Titanium to freeze the bloatware, I've had a look at the recommended ROMs which have options to disable loads of Samsung bloatware but I use a lot of them...
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505