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 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
OK, so I was preparing to flash a new ROM to my Sprint Samsung Galaxy S4. I backed up my original/stock ROM using TWRP Recovery and everything went well. I then flashed CWM to my phone and it was a bad ROM, so when I went to restore my original ROM, it installed great, however the boot process didn't backup. So now every time I turn on my phone, the Samsung Galaxy S4 logo shows up, but then blank screen with blue LED on. It would stay like this until I took my battery out. I need to know how I can restore my original ROM. Can I install a stock ROM, then restore my backup, or what?? Please guys I really need help.
Phone: Note 4
Version: 4.4.4 custom rom
Model: SM-N910F
Hi all looking for some advise. Rooted my phone a long time ago and never had a problem til recently. Within the last month my phone keeps going into boot loop and I need to put on charge to stop it, even if I have battery. Certain apps like the camera cause the boot loop and sometimes its just random.
Just wondering the best way to stop this? Isit safe to just install another custom rom over the one I've got and will that solve the problem? Haven't played around with custom roms in a long time so can't remember anything.
Any help would be greatly appreciated.....
Any suggestions please I'm desperate? Just getting worse my phone has to be on charge now or it goes into the boot loop every 10 mins or so.
make a nadroid backup and do a factory reset thru the phone settings? I'm thinking it could just be a misbehaving app update, if you didn't make any new modifications to your note 4.
imeem said:
make a nadroid backup and do a factory reset thru the phone settings? I'm thinking it could just be a misbehaving app update, if you didn't make any new modifications to your note 4.
Click to expand...
Click to collapse
I did that yesterday and it's helped a little. Still get the boot loop but not as often. The camera is usable now but I'm still getting the boot loop sometimes..... Any other ideas?
Install a different custom ROM or simply Odin flash a stock firmware.
Instructions of installing a custom ROM is stated in the OPs of the ROMs.
I encounter this many many times especially on Custom ROM.
The problem occur always occuring when my phone turned off because of empty battery, and charged it so I can open it up. This occur always in different Custom ROM. Always got stuck on Boot Animation. The only solution I found is wiping my data. But I'm so sicked and tired of backing up my whole rom using TWRP and restoring my Messages backup using Titanium Backup(because the apps can't be restored using Titanium Backup if you back it up using TWRP) so anyway, if you have encounter this kind of issue and have a better solution to fix this without wiping like using ADB, accessing system, logs to see what is the real problem of this kind of problem and so on.
Will be much appreciated
Flash a different ROM, or move to stock? Or don't let your battery run out completely?
Every custom rom i tried occur problem like this. I'm really not fond of Stock Rom so no. I already tried that but sometimes I keep forgetting it. It's still not a permanent solution
Well if you're not willing to try stock, sorry, can't help