Develop Bugs

OUCH - Recovery issue

Something happened to my phone. I rebooted, and it just loads to a screen with the signal bars.. Nothing else. I have already wiped, installed my backup, etc. Same issue.
I believe that it has to do with something being deleted while cleaning up my storage, I subsequently backed up after doing this, so that is likely the issue.
I am running rogue's recovery and I cannot get the sd card to mount so that I can put another rom on and flash. It just does nothing what so ever.
Any help fixing the mount issue?

Couldn't you just take the sdcard out and use a reader/writer to put the ROM on?
You could also flash the appropriate "NoData" version of the stock ROM in the ODIN links in my signature. They will preserve your user data and get you booted so you can do more advanced repair work.
Do not delete your nandroid backups even if you think they are bad since you may need to recover portions of them.

sfhub said:
Couldn't you just take the sdcard out and use a reader/writer to put the ROM on?
You could also flash the appropriate "NoData" version of the stock ROM in the ODIN links in my signature. They will preserve your user data and get you booted so you can do more advanced repair work.
Do not delete your nandroid backups even if you think they are bad since you may need to recover portions of them.
Click to expand...
Click to collapse
Worked like a charm, thank you!

HELP NEEDED with CWM "error while restoring /data!"

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?

[Q] Anyone else having Nandroid restore problems?

HTC One V [CDMA], Virgin Mobile US, original (pre-OTA) radio version, TWRP recovery
Has anyone else experienced flakiness with Nandroid backups on this phone? All of them that I've done with major OS changes—even after factory reset—have failed to produce a working restore even though they were taken from a working state.
I'm also unable to get back my previously-working CM 10.1 ROM even though I followed the exact same procedures (with the same files) that I used to get it working before.
This has been happening since my first failed Nandroid restore trying to go back from CM 10.1 to the HTC Sense Nandroid backup I made before attempting CM 10.1 in the first place. I thought this was due to the Sense Nandroid having been made under the OTA-upgraded radio version (I had to use the stock rom.zip from the RUU to get CM 10.1 working at all), but now I'm not so sure. I get the HTC logo and angry red legal text indefinitely now with those setups.
I can't even get back to the Nandroid I made of the stock HTC Sense ROM right after I restored from the RUU's rom.zip.
Anyone have any idea what I'm doing wrong? Or is this model really just that much of a pain?

Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.

riggerman0421 said:
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
Click to expand...
Click to collapse
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.

mynewshiny said:
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
Click to expand...
Click to collapse
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.

mynewshiny said:
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
Click to expand...
Click to collapse
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).

I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app

so as a conclusion, nandroid backup won't restore boot image? and the option in cwm advance restore>restore boot is useless? Me also always got stuck using nandroid restore

Ken-Shi_Kun said:
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
Click to expand...
Click to collapse
sellersj27 said:
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Confirmed that comparing file hashes isn't helpful for this purpose—I just downloaded scaryalienware's AFV as suggested and ran it against several of my Nandroid backups. It said all of them succeeded, including at least one of which I know will not restore successfully. However, of interest is the fact that it took about half as much time to scan the known "bad" one, and further analysis shows that it's about half the size of the others. I'll have to make some more backups via the various mechanisms to confirm that the size is an indicator; it may be simply that I had fewer apps installed when making those backups.
Too bad there isn't some kind of Nandroid Restore Simulator. But even if there was, this phone probably wouldn't have enough memory to use it. Checking Nandroid backups in a VM would be awesome though!

[Q] Help! Rooted 4.3, Backed up, and now cant restore backup

Hello, I recently rooted my wifes Note 2 that was on the latest OTA 4.3. Was not easy BTW. I did a back up in recovery of boot, system, and data. I figured I was good to go and start trying out other roms.
The first one I flashed was Macks Allstar 5.0 rom. Everything was great. Then my wife informed me that she did not have all of her contacts backed up to google and some were only saved to her phone. So then I figure I could just restore the original backup and extract the contacts and be able to install them to any rom.
Thats when everything went wrong. Everytime I tried restoring the back up,it would crash and recovery would do like a reboot. After many attempts I figured id try another version of recovery. After flashing many earlier versions of twrp and trying to restore, I finally was able to complete a restore from version 2.6. I was ecstatic. But then my heart sank again when boot always hangs on samsung logo. And that is where I'm stuck. I am able to flash other roms no problem but cant restore my original backup.
Needless to say my wife is ready to kill me.
Please if anyone could help me I would really appreciate it. I have searched throughout this forum and internet for hours and can not seem to find any help with this issue.
I am thankful to have been able to get this far with the help from the XDA community posts I never needed direct help even with prior phone rootings but this one has got me stumped. Thanks in advance

You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.

tx_dbs_tx said:
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
Click to expand...
Click to collapse
Thank you for your reply. I am at work right now and left the phone with my wife with a working rom. I will try phils recovery when I get home. As far as backups, I have two copies. One on my SD card and the other on PC but if they're both fried I guess that negates my efforts in redundancy. It's hard to believe the backup got corrupt so quickly. I have another backup of the 2nd rom I flashed and that one wont install as well.
Is there something I am doing wrong? If the backup file is corrupt, is there a way to extract contacts seperately out of backup?

Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry

ColeTrain! said:
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
Click to expand...
Click to collapse
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:

alexandnen said:
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
Click to expand...
Click to collapse
That's exactly right. Bootloader isn't playing well with TWRP recovery. Phil"s 6.0.7.9 seems to be compatible in most ROM vs bootloader situations. Don't use latest version of Phil's recovery as it doesn't work as well and most people recommend this as well.
If Phil's recovery won't flash your restore then Odin all the way back to stock unrooted LK8 ROM then root it with the Toolkit and flash TWRP from the toolkit at the same time. Then see if you can restore at that point.

Looks like this project has come to an end. My wife likes her new rom and doesn't want to let me work on her phone anymore. She was able to get most of her contacts back I will make sure she backs her contacts to google and I will try to convince her to install Titanium backup to backup all her app data.
Unfortunately all I have is a work issued iphone that I have no interest in jailbreaking. I really don't see the point.
I am still confident that I could have eventually restored her backup successfully with the help here.
Thank you tx_dbx_tx and coletrain for your help.

Xposed soft-bricked my phone..help?

I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help

stiarlitserenity said:
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
Click to expand...
Click to collapse
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.

Reflash rom, kernel and supersu. You shouldn't lose anything doing that.

sfhub said:
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Click to expand...
Click to collapse
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?

stiarlitserenity said:
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
Lesson learned bud. Half of the reason for TWRP and CWM is to have a full recent/current backup. Its always been like this. All roms, tweaks, xposed, write-ups or threads all say "make a backup" A backup is needed when something goes wrong. Notice the word "when" its not a if something goes wrong. Playing with androids involves way to much stuff and things do go wrong. Everytime your gonna do something just make a backup and delete your previous backup. Keep the backup on a sd card and delete the previous one. You put yourself in a situation like street racing on the freeway in a thunderstorm on new years eve. Not being a **** but for years and years now there a thousands of tutorials on this stuff. How to use adb, fastboot, twrp, soft brick, hard brick, de-brick tool. I don't know where the link is but I have a xposed script to flash in recovery that disables xposed and all modules from recovery in case of a bad module. If that can be found still I suggest that using xposed
FYI. The two replies before this told you what to do. If your looking for a easy everything is 100% going to be ok and you won't lose your text messages its probably not going to happen.

stiarlitserenity said:
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
If you are on the stock rom, flash the stock boot.img and stock system.img either in TWRP or via fastboot will erase any mods in /system (including Xposed). This will return you to a stock setup. Your apps, sms, and data would be retained.
To do this, download the factory image that matches your rom base. The July OTA is MTC19Z by the way. June is MTC19V, you'll have to remember which one you were on. This can be found on Google's Nexus factory image website. Next, unzip the downloaded file then flash the boot.img and system.img in TWRP (transfer the files to your phone). Alternatively, you could learn to use fastboot. Follow section 10 of this amazing guide by Heisenberg, but flash only boot.img and system.img.
You *should* be able boot up and learn from your mistakes as others have said. If you still have issues, factory reset and charge this loss to the game.
Sent from my Nexus 5X using Tapatalk