Not too often Im actually able to get a nandroid restore working.
For example, a few mins ago I wiped and tried to restore and got this error (using armon ra)
Error : run 'nandroid-mobile.sh restore' via adb!
Its quite frustrating. I actually changed to armon ra for this exact reason, as with clockwork sometimes Id get a similar problem when trying to restore about a bad md5 checksum or some such error.
As with most things, im thinking this might be user error, any ideas on this?
Well... I installed Vicious V2 of the Jellybean ROM (toro), and things were running OK. I used titanium backup to try to restore my SMS data, and found that I could not boot back up. It just bootloops. Since then, I have tried mutliple things, but nothing ends it...
I've tried:
*Restoring a NANDroid, but /data will NOT restore, and phone will bootloop.
* factory Reset/reinstall old AOKP ROM. It will not boot.
*Reinstall Jellybean ROM. Still bootloops
*I'm working on trying to get ODIN to detect my phone, but my computer won't stop detecting it as "Samsung ADB Interface". I've verified there is no response from ADB while in ODIN mode on the phone.
I just... can't stop the bootloops. There is another thread of the same issue, but his resolved over time. Mine doens't seem to be... I really want my phone to boot. The interesting thing is that none of my Nandroids will restore "Data". It just says "Completed in 0 seconds"
Are you able to use fastboot?
Sent from my Captivate
Yes.
Speaking of fastboot, I can re-flash my recovery just fine. I've tried everything on both Clockwork, and TWRP. Results are the exact same.
Same thing
Mine did the exact same after installing the same ROM after a TiBu restore (no system apps, no sms just regular apps with data). I tried wiping/reflashing several ROMs I had on the SD to no avail, all my nandroids would fail to restore data. I finally ended up using the Odin method I found to flash it back to stock 4.0.2 unrooted, unlocked. I lost all of my data on the SD card in the process.
I loved JB and would like to install again if I could find out what I did wrong to avoid this mess, any input guys?
Just a note: In recovery you have access to ADB. You can backup your SDcard with the command "adb pull /data/media C:\SD_backup"
It will save to... C:\SD_backup
If you get a file not found then, "adb shell", then "mount data", then "Exit", then try the adb pull again.
I'll keep messing with drivers then to see if I can get ODIN to detect me.
I'm an idiot. ODIN was seeing my phone the whole time. I just forgot where it shows that the phone is connected. I'll try an ODIN in the morning. I'm backing up my SD right now. I need sleep.
Edit: Nevermind.. It doesn't see it while in Odin mode.. but does see it on and off while booting into recovery.
Edit 2: I found that it was indeed a driver error. Fixed. Now back to backing up my SD card that I accidentally interrupted. I'll report back my ODIN results after I wake up.
my phone is doing the exact same thing
I was able to bring my phone back to life with ODIN restoring a 4.0.2 factory image.
So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium
Have a big problem: I want to install ZendroKat NAND to my Samsung Wave I. I did the install successfully exactly following the tutorial. With newest Kernel, dvmpatch is not needed any longer, it even causes problems making NovaLauncher crash all the time. Unfortunately, the tutorial did not point this out and so I have only known that when it has already been too late. How to get rid of this patch now??? Okay, I thought, again a full wipe, and then reinstalling without this patch. So far, so good. But reinstall does not work. When formatting the following error message is shown by cwm: E:format_volume failed to umount "/system" and when trying to restore the ZendroKat ROM, it stopped after formatting "/system" and shows "error while restoring /system" as output.
What to do now? Can anybody help? Bada has completely gone, /system is already reformatted - do not know to help myself now....
Try to unplug battery...
Then directly restart to recovery and try again...
Thank you very much! Left it without battery all night and have just succeeded to reflash! Now, all force closes of Nova Launcher have gone and I can try testing ZendroKat!
Help me find a solution with this error
E:format _volume :make_ext4fs failed
on dev/block/mmcblk1kp3
Error while formatting/system
Note: on kernal 4.5,while trying to clean the data
Turn device off by removing battery and boot directly to Recovery...
Format /system, format /data and then try to recover ROM...
I have a modified TWRP .28 and I have tried to restore a backup. It succeeded, but with a few errors.
The restoration reached 100%, but then it froze. I was unable to navigate the recovery, so powered of my device by pressing the power button. I figured that since it said 100%, the restoration process would be successful, and TWRP just froze. But once I booted up (because boot was successful, no bootloops), I saw that everything was fine, BUT I DIDN'T HAVE MY APPS, DATA, AND SETTINGS CONFIGURATION.
At least my backup wasn't faulty faulty... But if a backup messes up, you're screwed. If anybody knows what happen, please help.