Hi, guys, I have the flashing of custom roms down to an art now, but I'm trying to return to stock and now i have bootloops. I wiped the cache and dalvik cache, and wiped user data. I then selected to restore my nandroid backup, which was successful, but now I'm stuck in a bootloop when attempting to power on. It still shows my custom splash screen for a second then switches to stock splash screen and continues with the boot. Once it fully boots then it will reset. When I changed the splash screen I did use the p32img.zip method, but before I did the restore I renamed it so it wouldn't load it. Any ideas why it still shows my custom splash, and more importantly, what am I doing wrong to create the bootloops. I've considered just flashing a stock rom to replace my nandroid just in case I backed it up incorrectly (which is possible since this is my first phone I've done this on). Any suggestions or help would be much appreciated.
What ROM was your backup? Restoring a nandroid won't change the splash.
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
What ROM was your backup? Restoring a nandroid won't change the splash.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
it was the just the stock rom. 2.3.4 gingerbread. strange thing i just noticed is that if i boot into bootloader then connect to pc and reboot, then it won't bootloop....why is that? should i just flash a different stock rom and set that as my backup or are there things in the original nandroid that are specific to my phone? thanks for the reply by the way.
prachall said:
it was the just the stock rom. 2.3.4 gingerbread. strange thing i just noticed is that if i boot into bootloader then connect to pc and reboot, then it won't bootloop....why is that? should i just flash a different stock rom and set that as my backup or are there things in the original nandroid that are specific to my phone? thanks for the reply by the way.
Click to expand...
Click to collapse
Did you downgrade with tacoroot? Try flashing the .0312 radio.
Related
Ok, simply put, I am not able to restore a nandroid properly. I tried 2 different ones and when I reboot the phone just after the completion from recovery, it hangs on the white HTC screen forever (waited 40-50 mins before I took the battery out, with no luck). The "older" nandroid was restored succesfully a couple of weeks ago, so that's not the problem.
Any ideas? Thanks.
S-off and custom hboot image?
If yes make sure the hboot is not to small.
Sent from my HTC Desire using XDA App
Nope, S-ON. Recovery is AmonRA if it even matters, and the nandroids are MIUI_Au roms.
Sorry for double-posting, but just wanted to say I finally managed to restore the nandroid.
If it happens to anyone else, what i did was flashing the same exact rom the nandroid had in it. After that, back to recovery, wipe all user data and dalvik cache, and restore the nandroid.
Maybe it's something related to the kernel and not the rom itself. Anyway it's fixed.
I got the android over the boot screen and my phone wont boot up, It just happened when i tried to flash this mod but didnt read far enough to see my current phone state was not compatiable, what can I do, it changed 2 files.
MOD: http://forum.xda-developers.com/showthread.php?t=1089073
name:[mod][port]ec05_6_lockscreens[mod](froyo)[maddoggin]
gamerfantic said:
I got the android over the boot screen and my phone wont boot up, It just happened when i tried to flash this mod but didnt read far enough to see my current phone state was not compatiable, what can I do, it changed 2 files.
MOD: http://forum.xda-developers.com/showthread.php?t=1089073
name:[mod][port]ec05_6_lockscreens[mod](froyo)[maddoggin]
Click to expand...
Click to collapse
You'll have to Odin back to stock. Or restore your nandroid back-up, that I know you have..
Sent from my SPH-D700 using XDA App
NAnadroid backup being the one in CMW 3.0.2.5?
gamerfantic said:
NAnadroid backup being the one in CMW 3.0.2.5?
Click to expand...
Click to collapse
Yes, you did a backup before flashing anything, right? You could also reflash the ROM which is probably still on your SD card. Boot into Clockwork with 3 finger and reflash ROM.
Hi,
I'm having some problems flashing Google App and A2SD+ scripts on my CMv7 ROM. After flashing the scripts, the phone keeps hanging on the bootup screen, and I have to wipe my phone and reflash CM before it boots up again, which makes me lose all my configuration settings and app installations.
I'd like to know, if I do a Nandroid backup with CWM Recovery after I setup my phone to my liking and something goes wrong when applying a script, will restoring the Nandroid backup bring my phone back to the state right before script application?
Thanks.
goister said:
Hi,
I'm having some problems flashing Google App and A2SD+ scripts on my CMv7 ROM. After flashing the scripts, the phone keeps hanging on the bootup screen, and I have to wipe my phone and reflash CM before it boots up again, which makes me lose all my configuration settings and app installations.
I'd like to know, if I do a Nandroid backup with CWM Recovery after I setup my phone to my liking and something goes wrong when applying a script, will restoring the Nandroid backup bring my phone back to the state right before script application?
Thanks.
Click to expand...
Click to collapse
Yes. Restoring a nandroid returns your phone to the exact state it is when the nandroid is made.
Sent from my HTC Original Desire using Tapatalk
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
[SOLVED]
Hello guys, hope that someone could help me.
I had a 4.4.2 rom (note4neo 2.0) and i wanted to try 5.1.1 so first of all i mad a full Nandroid Backup through TWRP and also a titanium bkp. Later on i installed lollipop original rom through ODIN and everything was ok. I then followed a guide from Noble Rom for rooting and installing TWRP. Everything went ok, but i had problems with some rooting app (like titanium) and so i decided to revert back to 4.4.2.
At first I rebooted into recovery, made a full wipe (even system) then restored previously backup. Seemed to be ok, but then when rebooted it stucks on boot logo (i left booting for 28 minutes, so....).
Then i tried to wipe cache, dalvik and data and reboot again: no changes.
I then decided to reflash previously twrp (the one that i used for bkp). Flashes went ok, but i have "recovery is not seandroid enforcing" message on the top (even with the lollipop twrp: maybe is this the key of my problem?!?).
Restoring backup from older twrp didn't work as well...
Of course i can enter both Download and Recovery mode.
Now i flashed back the original 5.1.1 through ODIN in order to go back to original lollipop and see what u guys can tell me to do to restore backup i made..
Thank you very much for your help
I was thinking that maybe i should flash a stock 4.4.2 before restore the backup...
Now i'm downloading it and see what happens...tell me if i may be right
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
lennon123 said:
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
Click to expand...
Click to collapse
Update: Flashed 4.4.2, all ok. Then rooted, twrp and all ok again
After i restored Backup and stuck on boot.
Then i made again all the steps: STOCK, ROOT, TWRP, then Base version of the Rom and all ok.
At this point i was thinking it was done and restoring would have been just fine...unfortunatley it doesn't. Stuck on boot again.
So i reflashed the Base version of the mod rom and: it started with my restored app Btw i'm encountering problems like no home button, no volume icon, no settings shortcut. Now i made a cache and dalvik wipe but problems still remain..
Any idea?
After some attempts to solve those problems i stucked again on boot..
So now my plan is to: Flash STOCK rom, Root, Twrp, Base mod rom (everything always ok so far) and then restore JUST DATA from backup... Not touching system and boot should let the rom works just fine...at least i hope so :'D
Ok, as i was expecting the problem is solved. I did not restored System and Boot and all apps works just fine. Even though i miss some settings i made now i'm happy to be 90% back to origin ^^
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
lennon123 said:
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
Click to expand...
Click to collapse
Yes, it's solved I'll mod the title