Sigh... It got deleted once let me see if I can type this out again without losing it all...
So I went to update to the latest nightly this morning and cleared my cmupdater folder like I usually do before downloading it, then I rebooted and ran a TWRP backup which completed successfully. Upon rebooting the phone I was met with a spinning Cyanogenmod logo for about 20 minutes and nothing else.
I've searched around and someone said sometimes CM10 does this occasionally so I tried to flash the boot.img using fastboot, I tried several boot.img since I couldn't remember exactly which nightly I'm running. I had no luck at all.
So then I tried to use TWRP to recover to the 31st (today's) backup. Same thing. Then I tried using TWRP to flash the 31st nightly's update and same thing again. Spinning Cyanogenmod logo and me getting even more frustrated with this week's start...
Any advice where I go next? My next plan is probably to use TWRP to recover to my last successful backup just under a week ago.
digitLbraVo said:
Sigh... It got deleted once let me see if I can type this out again without losing it all...
So I went to update to the latest nightly this morning and cleared my cmupdater folder like I usually do before downloading it, then I rebooted and ran a TWRP backup which completed successfully. Upon rebooting the phone I was met with a spinning Cyanogenmod logo for about 20 minutes and nothing else.
I've searched around and someone said sometimes CM10 does this occasionally so I tried to flash the boot.img using fastboot, I tried several boot.img since I couldn't remember exactly which nightly I'm running. I had no luck at all.
So then I tried to use TWRP to recover to the 31st (today's) backup. Same thing. Then I tried using TWRP to flash the 31st nightly's update and same thing again. Spinning Cyanogenmod logo and me getting even more frustrated with this week's start...
Any advice where I go next? My next plan is probably to use TWRP to recover to my last successful backup just under a week ago.
Click to expand...
Click to collapse
Seems like you're probably gonna need to wipe data
WOW well I wish I could say I knew what had happened but it seems my 12/19 backup (ugh so far back for me...) restored it to working condition... Now the question is do I jump the loop and install the 31st's nightly! Lol.
With my luck the phone will just go nuclear at that point.
This happened to me and what I did to fix it was just flash the latest nightly like normal in TWRP and then reboot. Make sure to wipe cache/dalvik.
pOLLYpOCKET said:
This happened to me and what I did to fix it was just flash the latest nightly like normal in TWRP and then reboot. Make sure to wipe cache/dalvik.
Click to expand...
Click to collapse
I'll keep that in mind if it happens again. I ended up restoring to the 19th, updated all my apps that were out of date and downloaded missing ones, ran a backup today, then updated to the 31st nightly and it worked fine this time.
Your problem had a simple solution wipe data and system each time you flasha new Rom
Related
Hi, new here of course but read many posts about what my issue is at this moment. Just can't figure this out.
Steps I have gone through...
Rooted, installed 7.26 gapps, CM10 and d2vzw_recovery.img
flashed with 8.13 - no issues.
Saw 8/14... rebooted into recovery, wiped dalvik, and flashed 8.14. Ever since then i am in a boot loop. Recovery back to 8.13 and i even wiped everything and still same.
Any ideas?
I am rooting back to stock with Odin now, hopefully that fixes it and i can start over.
think I figured it out
Looks like I accidentally wasnt using the right CWM recovery. Lost data, but didnt have much to lose.
8.14 on the S3..
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Did you try to wipe cache and dalvic cache in CWM?
Dizzyrul3z said:
Did you try to wipe cache and dalvic cache in CWM?
Click to expand...
Click to collapse
No. I just make a dirty flash over the Cyanogemod-Updater under Settings.
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Volkan66 said:
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Click to expand...
Click to collapse
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Volkan66 said:
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Click to expand...
Click to collapse
What recovery do you have installed?
january waower
kieranc said:
What recovery do you have installed?
Click to expand...
Click to collapse
I have installed ClockworkMod-Recovery (CWM): cwm-6.0.4.6
I don't have any problems with the recovery but with the Nightly Update from 27th February.
I can't understand how the cm-11-20140227-NIGHTLY-falcon can get official, when a lots of people have the same problem: bootloops.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I totally agree with you. I won't do a full format of the internal card. Just waiting for the next Nightly in the hope that dhacker improves this issue.
Do you have also problems with GMAIL. After each restart GMAIL is lost. I must install it each time new.
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
kieranc said:
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
Click to expand...
Click to collapse
So, I installed by mfastboot for now the newest stock rom 4.4.2 DE, updated to the latest release and rooted.
Maybe I'll flash also kernel to faux's release. Very strange issue. I flashed CM several times and today's issue was the first time.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I've just wiped /data/media ("sdcard") and have successfully installed and booted feb 27th build. Strange problem but that looks like the solution....
I was at the 0224 build and flawlessly updated to the 0227 build... no issue so far. i am using twrp...
Hey guys,
i have flashed the newest Nightly cm-11-20140228-NIGHTLY-falcon.zip today and everything was solved. No bootloops or lost of apps.
With pink kernel the system rocks. This is awesome. Thanks to dhacker29, pinkflozd, faux123, razrqcom-dev-team :good::good::good:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
hydromän said:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
Click to expand...
Click to collapse
I can confirm your sound problem.
I am using the nightly version 0228 and pink kernel 0228 and would recommend you to use the pink kernel because you will feel the boost in performance.
Yes the battery will drain a little bit more than on stock-cm but it is worth it. I can use my phone with pink kernel two days long without charging it.
So I will try Again Pink Kernel =).. I hope the Sound in Call Problem get fixed soon
Android-CM11
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
hydromän said:
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
Click to expand...
Click to collapse
Yeah this version of pink kernel is great. I hope this kernel will leave soon the beta-stadium and will get official.
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
tohigh said:
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
Please flash the TWRP 2.6.3.3 recovery first then flash the newest nightly cm-11-20140304-NIGHTLY-falcon.zip .
I am using 0303-NIGHTLY with TWRP 2.6.3.3 and don't have such issues like bootloop again.
But it is very important to flash the recovery first, then flash cm-11-20140304-NIGHTLY-falcon.zip with Cyanogenmod-Updater under settings.
If you do otherwise flash cm first you will encounter the same problem.
So I haven't used my Xoom (wifi) in literally 2 years or so, I grabbed it from the basement today thinking I'd update it and see what I could do.
I jacked it up pretty good as fsr as I'm concerned and not knowing what to do since its been so long.
I was running eos rom and running their nightlies like (46) or something.
I realized I didnt have my gapps (no playstore etc). I booted into recovery and realized I had twrp 2.3.3.0. I went into the dev section and found twrp, the bigpart one and was going to flash cm11. I downloaded the newest twrp like 2.6.3, booted into recovery and flashed the new twrp version. I had already out cm11 on my sd card and was proceeding to wipe everything as it said to do, I wiped my stuff and it kept saying failed. I went ahead and flashed cm11 thinking it was just saying failed and it cleared everything.
When it xomes up it says it needs to be reset, I hit reset it takes me to recovery and the twrp blue welcome screen is stuck, wont let me into do anything
What do I need to do, can anyone please help me?
I have encountered a strange problem. Please help.
1. I was running CM12 nightly (April 10 build). I also have TWRP backups of Apr 8 image and my old CM11S (44R) image.
2. I downloaded OxygenOS to try it out. Booted the phone into TWRP and tried flashing the ZIP.
3. Got an error while flashing the ZIP.
4. Rebooted the phone into recovery and tried restoring the Apr 10 image.
5. Restore says it is successful.
6. On reboot, the phone stays on the "Powered by Android" screen. It does not boot up into the ROM image. It boots up into recovery instead.
7. I tried the same process with Apr 8 image and the same issue.
8. Finally, I restored the backup image of CM11S and that works well.
Can someone please advise how can I get my backup ROMs to work?
I have now tried backing up ROMs for Cyanogen CMOS12 as well as Oxygen. None of the restores are working. I am backing up all partitions. Where am I going wrong? The restore does not give any error, but the boot is stuck at the logo. When I restore CMOS12, it gets stuck on the screen that says "Cyanogen". When I restore Oxygen, it gets stuck at the boot animation of Oxygen.
I am using TWRP 2.8.6 for restore and Online nandroid manager for backing up.
Is it possible that OnlineNandroid manager uses a different version of recovery for backup?
Please help.
.
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
JeffDC said:
I'm new to the CM 12 stuff but I thought I read that TWRP had an issue with compression during a certain range of weeklies, and due to that, would/could not restore from that range.
I think I also read to make sure you have the most up to date TWRP, and a weekly after 4/22, or so. I don't recall the exact date of the compressed weeklies causing the issue,but I think the compression problem began in April, sometime. Hopefully someone will come by and further clarify or identify your issue.
What version of TWRP do you have and what's the date of your weekly?
Click to expand...
Click to collapse
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
see if this link has any relationship to your general issue
https://forums.oneplus.net/threads/...cm12-1-nightlies.300277/page-78#post-11010591
read around a bit as some folks seem to have had the same issue as you, there is also an xda topic for the nightlies, as well which may be a good place to search
indoliya said:
I am using TWRP 2.8.6. I have tried restoring Oxygen, CM12, CM12S backups and none of them are working. Restore takes reasonable time and says it was successful.
Click to expand...
Click to collapse
Did you wiped cacha/Dalvik? I personnaly do these wipes before and after flashing/restoring.
If I were you, I'd try to flash the latest cm12 nightly "on" you restore, maybe it could help..
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
real_sl4cker said:
You might have to flash the right firmware for the CM 12/11 you want to restore. TWRP doesn't backup firmware by default, only ROM/Data. So flash the right formware for the ROM you want to restore and then restore your nandroid.
Click to expand...
Click to collapse
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
indoliya said:
Thank you! Previously, I was switching between CM11 and CM12 without any problem. Are you sure about this?
Click to expand...
Click to collapse
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
real_sl4cker said:
Not sure as in "Yes, that's the way to go, do it!" but it's worth a try. I haven't switched back to CM11 from CM12 (updated to CM12 just yesterday) up to now.
What I'm pretty sure about is that TWRP (by default) only backs up system and data, no modem and stuff. And CM11 and CM12 come with different firmware. Flashing the right firmware for your build won't do any harm anyway
Click to expand...
Click to collapse
Finally resolved this by going to Online Nandroid app and changed the shell to default and busybox to default. Now the backups taken with these settings are getting restored successfully.