Database Info

Phone won't load if I try to restore after installing Baked Snacks 1.6

I made a Clockworld backup file before flashing to Baked Snacks 1.6. Everything is running fine but I'd like to restore all of my previous settings. However, when I try to do so it just hangs on the Samsung screen. The only way to get my phone running again is to do a wipe and then reflash the Snack rom. I tried just restoring data under advanced settings to no avail as well.

[Q] Stuck at bootscreen

Hello,
Im using the TeamRogue's recovery (1.3.0) and I made a backup using this, before trying out a rom.
Now i wanted to go back to my backup, so i restored it, however it is stuck at the asus eee pad screen (boot screen).
I've seen more people with this problem and some say wiping the cache after the restore fixes it. Or when using the Super Wipe script, reboot after wipe and then restore.
Now after a lot of tries and wipes i finally got it booting fine.
However, me as stupid as I am, I tried another rom, so now I got the same problem, however only this time i can't get it to work.
Any help appreciated!
Kind regards,
ps. sorry for the grammar mistakes

What ROM were you on when you made a backup and what ROM did you try out?
If you went to an ICS base ROM and went back to a HC base ROM, you must get a HC kernel back, you can achieved this by flashing the HC ROM after your backup is done restoring.

I was on ICS and i flashed a ICS rom.
I also know about the kernel thing, ive flashed to my 3.2 backup to with no problem.
It just hangs on boot, has to be with \boot partition

Saw a few reports of this in the Team Rouge thread.
Same way to fix, nandroid restore and once it's done. immediate flash the ROM the backup is based upon. (No wipe if you want to save your data).
I had this happened to me going once going to an older ICS backup.

So.. to make this clear, i made a backup of the stock ICS.
So, i have to restore my backup and then flash a stock ICS rom or will EOS or some kind work to?

pretty much it is because eos is asop and stock is stock and some things that are different between the two are not restored when you restore a nandroid

Can't Restore From TWRP

I downloaded Trickdroid and everything is good. before I did the download I backed up stock in TWRP.
When trying to restore stock it says 'completed' in about two seconds and when I then reboot I'm still on Trickdroid.
Was I meant to do a nandroid in cwm? Can't think why TWRP wouldn't just restore.
Obviously I still have the stock image on my sd card in the recovery folder of TWRP, so would there be any other way of flashing/installing it whilst bypassing TWRP if I have to?

I faced a similar problem and I freaked out. I installed MIUI to test it and then after I tried to restore my Trickdroid nandroid. Every time I boot the phone after restoring, it kept asking if I want to use the miui launcher and then an error appeared saying your phone has stopped and nothing works.
I did wipe everything (system, data, cache, dalvik) but the same thing happened over and over. It also refused to install any new ROM. I thought I had a brick. Then after a couple of reboots to recovery, I could install a fresh trickdroid and then on top of it I could restore my nandroid.
Now I am weary of installing anything new. I have a CWM nandroid as well just in case.
Sent from my HTC One S

I included a script which does not allow you to switch from Trickdroid to another ROM as it's the best anyway
Just kidding, try to reflash your Recovery or so

Just had an idea, would it make a difference if I flashed the new boot.img before wiping the current ROM? meaning, before restoring trickdroid, I flashed the kernel of trickdroid.
Because yesterday I had the same experience again this time with CM9 and I had to make a fresh install
Sent from my HTC One S

torxx said:
I included a script which does not allow you to switch from Trickdroid to another ROM as it's the best anyway
Just kidding, try to reflash your Recovery or so
Click to expand...
Click to collapse
Don't worry, I'm sticking with trickdroid, just wanted the peace of mind of knowing I could go back to stock anytime.
Now I can't, I'm stuck with you

[Q] Custom firmware issues..

Howdy.
I've been using custom firmware since I got my phone over a year ago, but I'm now having big issues.
I tried to install a 4.2.2 ROM and couldn't boot, even after trying bunch of times, clearing cache, all that jazz..
So.. usually I would just put on another ROM or just restore from a backup, but I'm stuck in a weird situation.
I have a bunch of ROM backups (Clockwork Mod Recovery) going back to April last year, the 1st one is standard AT&T, then various custom ROMS (last one I used was Cynogen 10).
But I can only restore the first AT&T ROM, nothing else will restore. I also cannot even install any ROM the only way I can get a working phone is to go back to the horrible original AT&T ROM..
Clockwork mod recovery also crashes when I try to wipe cache, so think that maybe a clue....
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks

eckythump said:
Help!! I don't want to be stuck on AT&T ROM forever.... I miss Android 4.1 features
Thanks
Click to expand...
Click to collapse
What version of CWM are you on?
You can always restore to your AT&T backup, transfer all of your other backups to your external SD or computer, ODIN to stock, do a complete wipe of the phone, flash the most recent CWM from Sk8 and try again. I'd say that's your best case scenario.

mrfeuss said:
What version of CWM are you on?
I'm on 6.0.1.4 which I believe is latest. I can't even get the original ROM to restore now either. Ughhhh hope I'm not bricked.
Click to expand...
Click to collapse

Try Odin back to stock before u do brick it that should fix any problems

Random Reboots

I was on CM10.1 for a very long time, and just recently decided to flash something newer. So I tried flashing Philz recovery (had CWM), then used that to flash VRUBMF1 and VRUCML1 baseband afterwards (from this thread). Without booting my phone, I then flashed CM11 and the kitkat gapps. When trying to restore apps through Titanium Backup, I got a random reboot. Since then, I would get many random reboots, most often in the middle of a Titanium Backup restore of my user apps because it's the first thing I want to do. Sometimes the phone will reboot before even getting to the app restore. I have tried flashing PAC rom (4.3--I flashed jb gapps with this) and unofficial Paranoid Android (4.4) as well, and the problem persists no matter which rom I am running. Of course, I have tried reflashing many times.
I am also trying and currently on TWRP, but this hasn't helped. Going back to CWM and trying to restore my CM10.1 backup gives me a fail error.
Before each flash, I wiped data, and rewiped cache and dalvik afterwards too. Is there a problem in my flash process? What can I do to solve this issue?