Database Develop

Need of help with errors in Clockworkmod Recovery

I am trying to create a back up of my system and the backup errors out in the data portion. It does not say why. Just says error when backing up on /data. I am currently on a rooted stock rom. I have tried using older versions of clockworkmod recovery with no success. Any help would be greatly appreciated. THANKS!
Sent from my DROID3 using XDA App

Are you using Koush's or Hashcode's versions specifically for the d3? Im asking because I thought there was only 2 versions and you said you tried older versions.
Sent from my DROID3 using XDA App

I used them both. Koush offers to flash older recoveries which is only 2 so far. I currently have hashcodes version and the same thing it going on.

I flashed the stock deodex via clockworkmod recovery and it worked like a charm. I then downloaded another zip and tried to flash it then i could no longer boot into clockwork recovery. So to solve that i deleted the d3 bootstrap then redownloaded it and i could boot into it again. So maybe try that then try a backup again? Im not sure why you would be getting an error
Sent from my DROID3 using XDA App

Well, you have to redo the bootstrap on droid 3 after every fresh install of a new ROM. I have tried deleting the bootstrap and reinstalling it with no success. It still errors out on the backup of the data portion. Maybe I might take a risky move and flash a new ROM without a backup and see if it is able to backup the data after the install. I hope I just don't brick my phone or get a bootloop. I would be screwed!

Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!

mothman57 said:
Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Maybe you have a corrupt fat filesystem on the backup destination...
Have you tried to do a checkdisk when connected to the pc ?

I just completed a checkdisk and I even formatted the SD Card yet still the same issue! I then tried to checkdisk the partition of the internal memory yet no success. Thanks for the help though. It is greatly appreciated.

Steel Droid 3 came out today. I installed the new ROM and still it errors out on the /data portion of the backup. Hopefully someone can help me here. Last resort is a full factory reset of the device. I am waiting before I do that.

Is anyone else experiencing these same issues?

Try SBFing, re-rooting and then using the tweaked boot-strapper. When all else fails, start from scratch. If that's still not working, I would venture to guess that your /data partition has issues (which SBFing should fix).

What OS are you using?

I'm having a different problem that maybe some can help with. I just flashed the sbf again, and I've rerooted stock, and now I'm trying to reflash SteelDroid3.
I'm running into an error I haven't had before with CWR. Everytime I try to flash any ROM (from internal or external) it fails - E:Can't open "location" (bad)
I've checked MD5 sums and tried muliple roms, all give the same error.
I started with Hashcodes tweaked Bootstrap, then uninstalled and tried koush's. Neither made a difference. I even tried CWR 5.0.2.5 vs 5.0.2.6 to see if that would make a difference. No luck there either. Even tried reflashing the SBF, still no go after getting reset up.
I can make nandroids, and I can restore nandroids, (restored a debloated I had made earlier no problem) So the only issue is flashing a new rom.
Any idea's
Thanks

I have windows 7 64bit on my computer. Android phone is the 2.3.4 with steel droid v3 ROM. As far as SBF goes, should I use the example on the android development section of RSDlite? And if I preform this, will it delete all my data/apps and restore it to like a factory reset?

Im having similar issues. Backups are not being created properly - the zip files only contain 2 files:
data.ext3
system.ext3
I have one backup that works from a week ago - it contains the following files:
.android_secure.vfat
cache.ext3
data.ext3
nandroid.md5
system.ext3
any ideas why backups wouldn't be created properly? (using the modified bootstrap and CWM)

That is exactly what I am experiencing as well. Just the system and data are being preformed, but the data is not properly finishing.

I think we just need more room on our SD cards. I cleared up a few gigs of info, and now its working just fine. give it a shot.

I dont think that is the issue. I have 14.6gb worth of free storage on my card. It has to be an issue with my internal storage or clockworkmod. I am guessing it is my internal storage.
Sent from my DROID3 using XDA App

Well, I decided to do it. I flashed the original unrooted ROM back on the phone. I have to say it sucked redoing all my phone tweaks, but it did fix the issue. I can now preform back-ups in full! Thanks for all who replied in this forum.

[Q] AT&T Note 3 4.4.2 unable to mount system

I have a new n900a with stock 4.4.2. I rooted the phone with the TowelRoot and then installed SS 4.72. I backed up my phone with a nondroid backup via SS, titanium backup as well as Helium all on my external SD . The problem is that I tried to flash the Alliance ROM v6 and it didnt work. So I said, hey I've got a full backup lets just restore to the stock ROM and no foul. Well it happens that it FAILED and I noticed that SS cant mount the system partition.
From what I have read, the stock system file for AT&T is not available so I cant flash a stock rom back on my phone. I think that somehow the phone got corrupted. I tried wiping, format data, delvic cache, data, etc. via SS 3.72, nothing works. SS shows the system partition empty. I suspect this may have happened because the ROM I was flashing was based on using SS 3.71. The developer said I should not have a problem flashing the ROM with SS 3.72. I've been flashing roms for a couple of years but have never come across this and am totally stumped. Can anyone point me in the right direction or do I have an $800 brick?

ccaceres said:
I have a new n900a with stock 4.4.2. I rooted the phone with the TowelRoot and then installed SS 4.72. I backed up my phone with a nondroid backup via SS, titanium backup as well as Helium all on my external SD . The problem is that I tried to flash the Alliance ROM v6 and it didnt work. So I said, hey I've got a full backup lets just restore to the stock ROM and no foul. Well it happens that it FAILED and I noticed that SS cant mount the system partition.
From what I have read, the stock system file for AT&T is not available so I cant flash a stock rom back on my phone. I think that somehow the phone got corrupted. I tried wiping, format data, delvic cache, data, etc. via SS 3.72, nothing works. SS shows the system partition empty. I suspect this may have happened because the ROM I was flashing was based on using SS 3.71. The developer said I should not have a problem flashing the ROM with SS 3.72. I've been flashing roms for a couple of years but have never come across this and am totally stumped. Can anyone point me in the right direction or do I have an $800 brick?
Click to expand...
Click to collapse
Head on over to the soft brick thread for instructions on how to undo what you did. If that fails, well, you always have the hard debrick method.

[Q] Did CM installer brick my phone?

Soft brick after CM installer
Hi guys, I could really need some help here. I tried the Cyanogenmod installer and everything went fine, except my phone was stuck in
bootscreen for too long time (never booted).
In CWM recovery I did a factory reset/wipe, reboot, but to no avail; still stucked on CM bootscreen.
I then tried to flash CM11 by recovery sideloader. This goes to 100% and recovery says "Installing update", but nothing happens.
Is it supposed to install and finally reboot by itself, or should I do something?
I tried to installed zip from SD-card, but got "E:Can't mount /sdcard". I guess that means that I can't push the .zip over ADB to /sdcard
either.
What else can I try?

Edit: I wiped /data and then I could suddenly push the .zip to /data/media and the, finally flash the .zip from sdcard!
Why on earth the installer didn't wipe everything from the beginning, I don't get...
Did I miss anything obvious about the wiping thing?

A factory reset should do the trick normally. But if you ever get a message that you can't mount something you have to wipe that partition in recovery. I haven't used CWM in a long time. I prefer twrp as a recovery these days
Sent from my HTC One using XDA Premium 4 mobile app

Thanks, I'll remember that, should it ever happen again. What's the benefit for TWRP over CWM?

in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.

Ayman.y88 said:
in Htc One i always had this problem.
I'm pretty sure you will never be able to mount SD
but its not a big problem since you can still sidepush the zip file.
and to be honest there is not much difference between TWRP and CWM . its a matter of preference.
On my Htc one i always used TWRP but on other android devices for some reason i sticked with CWM.
Click to expand...
Click to collapse
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!

sblar said:
Unfortunately, I was not able to sideload the image, the transfer went well, the phone said "Installing update" but nothing happened!
Click to expand...
Click to collapse
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL

Ayman.y88 said:
i guess u will have to install back the official ruu and after it add the rom u want to flash on the sd card and flash it ...
let me know if it works with you.
GL
Click to expand...
Click to collapse
Post 2 implies op was able to flash the zip successfully after wiping /data.

Correct, and I could probably also have sideloaded after wiping /data...

[Q] AT&T Samsung Galaxy Note 3 UnRoot/Stock Firmware. Q

Hello there I am new to this not that new but ya I've been rooting phone for a while know never had no complications what so ever but here comes the boom lol. AT&T SAMSUNG GALAXY NOTE 3 I recently used TowleRoot & Safestrap everything went find I created a slot for rom first backing up my stock rom I went ahead added the rom. I was not satisfied with the romantic so I went back and did factory reset wipe and advanced wipe and it messed up my stock rom I am not able to load a romantic to it or load my back up so I am using the slot I created on safestrap the thing with this is that some how this is taking all my system memory I can't download unless I have a sad card on phone at this point I don't know what to do I tried using odin also oneclick alway get fail on both well in the process of doing this well trying to fix it I saw that a lot of people have been having trouble fixing this some are on boot logo loops others bricked and we'll I want to find out if any body here in this community can help me and others to save the note 3 thank you for your time.

You should be able to use the same backup of your stock Rom that you're using in slot 1 and restore it to your stock slot. I'd do an advanced wipe of your stock slot leaving only wipe sdcard unchecked but wiping everything else. If that doesn't work and you were on NC2, then this will help.
http://forum.xda-developers.com/showthread.php?p=54807112

andygev35 said:
You should be able to use the same backup of your stock Rom that you're using in slot 1 and restore it to your stock slot. I'd do an advanced wipe of your stock slot leaving only wipe sdcard unchecked but wiping everything else. If that doesn't work and you were on NC2, then this will help.
http://forum.xda-developers.com/showthread.php?p=54807112
Click to expand...
Click to collapse
Hi! Andygev35 Thank You so much for your replyI was able to restore backup in slot 1 it is still using all of my hard drive memory 32g device capacity and this slot is using 29.57 gb.

Did you delete slot 1? That will also take up available space.

andygev35 said:
Did you delete slot 1? That will also take up available space.
Click to expand...
Click to collapse
Yes I andygev35 did but I had to create it again to install back up I did a advance wipe before install phone came on with my stock rom everything wipe but ya it is still taking up all my memory p.s I still have not try the link you send me I did this on safe strap.

I'm sort of lost with what you did... What you should do is delete rom slot 1 altogether, do an advanced wipe of the stock slot, uncheck wipe sdcard, then do a restore to the stock slot with your backup file.

andygev35 said:
I'm sort of lost with what you did... What you should do is delete rom slot 1 altogether, do an advanced wipe of the stock slot, uncheck wipe sdcard, then do a restore to the stock slot with your backup file.
Click to expand...
Click to collapse
Sorry for confusion Andygev35 I did do that I erased slot 1 I also did do a complete wipe on stock rom before I tried installing my stock back up it says E:unable something system let me try it again. Sorry one again I am new to the forums.

K1NGB345TNOTE3 said:
Sorry for confusion Andygev35 I did do that I erased slot 1 I also did do a complete wipe on stock rom before I tried installing my stock back up it says E:unable something system let me try it again. Sorry one again I am new to the forums.
Click to expand...
Click to collapse
ok I try it again when I do a advance wipe it says E: unable to mount ' / system when I try restoring back up to stock rom both system and data are checked I hit ok and I get same thing E: unable to mount system so I tried reboo t and it tells me no os installed

It sounds as though you may have used either an outdated version of safestrap or even the wrong version entirely. Best bet is to head over to the link I sent earlier and Odin back to stock 4.4.2. Then you can towelroot again. Make sure you use this version of safestrap: http://forum.xda-developers.com/devdb/project/dl/?id=7216

andygev35 said:
It sounds as though you may have used either an outdated version of safestrap or even the wrong version entirely. Best bet is to head over to the link I sent earlier and Odin back to stock 4.4.2. Then you can towelroot again. Make sure you use this version of safestrap: http://forum.xda-developers.com/devdb/project/dl/?id=7216
Click to expand...
Click to collapse
Hey Thanks a lot you don't know how much I appreciate this I just went a head and use the link you send me work awesome I have my phone back so cool thanks again for everyone else this four links are gold thank you again @andygev35 .:good::laugh:

Glad to have helped.

SS 3.75, Stock rooted, can't flash roms. Unable to mount system

I can't imagine what I'm doing wrong here. Steps I'm taking (rather circuitously I might add):
1) Odin back to stock 4.4.2
2) Root
3) Install SuperSU, Busybox, & SS 3.75
4) Reboot to recovery
5) Backup stock software
6) Reboot to recovery
7) Flash rom according to instructions
What happens is that it writes the data section, but not the system. So I'm left w/ no OS on the phone and have to Odin again to get it back up. After the initial backup (or even if I skip the backup), I get an error in SS "unable to mount /system"
I've searched high an low through the SS thread and so far have not been able to glean anything close to the problem I'm having. Is there something I'm doing wrong?

Could iy be your sd card?
janderfu said:
I can't imagine what I'm doing wrong here. Steps I'm taking (rather circuitously I might add):
1) Odin back to stock 4.4.2
2) Root
3) Install SuperSU, Busybox, & SS 3.75
4) Reboot to recovery
5) Backup stock software
6) Reboot to recovery
7) Flash rom according to instructions
What happens is that it writes the data section, but not the system. So I'm left w/ no OS on the phone and have to Odin again to get it back up. After the initial backup (or even if I skip the backup), I get an error in SS "unable to mount /system"
I've searched high an low through the SS thread and so far have not been able to glean anything close to the problem I'm having. Is there something I'm doing wrong?
Click to expand...
Click to collapse
I don't know if this would help but have you tried the process with a different SD card? I was having problems and thought it was something I did wrong but found out my scan disk 64gb micro SD card was the problem. Hope you get it working, good luck Janderfu

I tried that last night. Same result. For some reason I can read from the system partition, but not write to it.

some have reported issues where if you wipe system, it messes up the sd... if you are able to odin just fine, then when in SS, just do the factory data reset option to wipe and dont do the advance and wipe system.. then see if you are able to flash this way.. just make sure to do the factory reset like 3x to be safe and then flash..
see if that works.. also what version of SSare you using and what version are you on as in JB or KK... i see you say 3.75 up top, but to be sure you are on NC2/KK?
From my Fired-up Note Pro 12.2!

I'll give that a shot.
When I go back and Odin, it's going to NC2/KK. And yeah, the SS is 3.75.

janderfu said:
I tried that last night. Same result. For some reason I can read from the system partition, but not write to it.
Click to expand...
Click to collapse
I get a similar issue in trying to run init.d scripts. Several times a "can't mount root as read/write" error is shown. I'm interested to know if this is similar and how to approach as well. Thanks.
~Sent from my AT&T Samsung Galaxy Note 3 Badass~

janderfu said:
I'll give that a shot.
When I go back and Odin, it's going to NC2/KK. And yeah, the SS is 3.75.
Click to expand...
Click to collapse
Did it work with the factory rest without wiping the system in advanced wipe? If not than just to make sure that you are flashing the custom rom in one of the rom slots and not on the stock rom partition (just making sure because sometimes we make small mistakes as a noob).