yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic General] NoaT:
well it looks right

it shure does look like a solution too my problem but the thing is i have no clue where as to find the

- boot.img

- cache.img

- data.img

- misc.img

- recovery.img

- system.img

files i need:confused:
[myTouch 3G, Magic General] odanion:
well I have found those files needed ( I too partitioned my SD and lost everything) But when I load fastboot commands it returns with

FAILED <remote: not allow>

for everything I try to do
[myTouch 3G, Magic General] PiCkLeS:
one more..

So I am also in the same position, and my problem is that when I do the fastboot erase that works fine, but when I try to flash the img-files I have from the nandroid-backup, it says:

$ fastboot-mac flash system system.img

sending 'system' (85962 KB)... OKAY

writing 'system'... INFOsignature checking...

FAILED (remote: signature verify fail)

$

..for each of the images and places (cache, system etc)..

Any ideas?

//N
[myTouch 3G, Magic General] bonesy:
you have perfect spl. See this thread
[myTouch 3G, Magic General] sitimber:
why don't people put the sdcard in an adapter and plug it into the pc and copy nandroid back to the card
[myTouch 3G, Magic General] bonesy:
if you can boot to fastboot (back + on(red phone) its not over yet!

Are you on 32a? if so search the forums for sappimg.zip
[myTouch 3G, Magic General] lpasq:
exactly! that would have been the way to do it more simply :o

another easy process i like now that isn't much discussed is that of using SU File Manager & Terminal (SUFBS) to delete and add .apk files intead of doing the whole AndroidSDK ADB thing...
[Touch Pro, Fuze ROM Development] schwags:
I've tried a few different custom ROMs on here, and recently most seem to be sufferring from the same issue. It's been happening to me for a couple of months now, I'm not sure if it's a 6.5 bug, or some other software package or whatever. I will say I just recently got a replacement phone for another problem, and it's doing the same thing as my old phone. At my work, we require a 4-digit password and for the phone to lock within an hour for our Exchange server sync.

For whatever reason, when I put custom ROM's on there and sync, within about 3 days at most my device will totally wipe. It wipes the storage card, everything. And it's a real pain in the ass to try to keep my settings for very long. I'm just curious if anyone else is seeing the same issue? I just figure, probably not a lot of people require a password so it doesn't happen to a lot of people. It seems to only affect 6.5 ROMs for whatever reason.
[Touch Pro, Fuze ROM Development] schwags:
Shameless bump. Sorry, just want to make sure, someone has to have seen this, maybe not though.

I can really only confirm this happens on two ROMs. I don't want to call anyone out because it might be a WM6.5 bug and not a chef's fault.
[Touch Pro, Fuze ROM Development] stickynugz:
sheps rom works for me, it is the only rom I have used so i cannot confirm your question about other roms not working. good luck and if i were you try Sheps rom, very fast and stable rom, and it looks good to.

http://xdaforums.com/showthread.php?t=497699
[Touch Pro, Fuze ROM Development] dapirate:
I use exchange at work and have only seen this once, and the problem for me was the security code was input incorrectly more than 7 times and all data was erased even the microsd card. I was quite pissed but thats the only time I've seen it.
[Touch Pro, Fuze ROM Development] schwags:
It's similar to that, it used to be where I would leave the phone sitting there for a while and come back to it and it would say "if you input your password incorrectly one more time...blah blah". And no matter what i do, it would wipe my device. Now usually i just turn the screen on and the skinned keys don't show up, it's just the old one. Pressing the keys does nothing at all, i usually reset the device, then it wipes on the next reboot.

at one time i thought it was related to either plugging it into the charger or a computer because it would usually do it right after that. I see it happen no matter what now though, i could just have it sitting there and it will do it.

Well obviously one of them is NRG's ROM, I have also seen this in TPC's ROM. Hard to say what's similar between the two...I can't confirm too many others though as I don't usually switch that often, just when the one's I like to use update.
[Touch Pro, Fuze ROM Development] hshortt:
Yep. I've had the very same 'feature' happen to me too. Cannot properly identify what's causing it either.

Cheers
[Touch Pro, Fuze ROM Development] debonairone:
Have you checked with your Exchange Admin... I believe there is a feature that allows them to remote wipe (or at least setup the parameters) devices attached to the server... They may be wiping your device because it shows up as a foreign device... Just stabbing in the dark, it may not be a rom based issue, but an exchange issue... It happens with custom roms, did it happen with the stock rom...?
[Touch Pro, Fuze ROM Development] schwags:
Good suggestion, although I am the Exchange admin, so no, I'm not wiping my own device.

I have never seen it happen on a stock ROM, although I usually don't have one on for very long. I've never seen it in 6.1 either, just 6.5 ROMs from about late June thru now.
[Touch Pro, Fuze ROM Development] schwags:
OK, 3 ROM's now, RRE just did it to me. It must be a 6.5 bug or an Exchange server bug.
[Touch Pro, Fuze ROM Development] fallingup:
well i run 6.5 and use exchange 2007 for my business, havent seen this happen at all on any rom. I dont have any pin required for my devices, but i can turn that on just to test for you.
[Touch Pro, Fuze ROM Development] schwags:
That would be cool if you could. I have a feeling since it happened on two phones and multiple ROMs that it will happen to anyone. I just feel that no one really requires a password. Just make sure you set a maximum number of attempts before wipe, I have the default of 8 set. Use one of the ROMs I mentioned if you don't already.
[Touch Pro, Fuze ROM Development] shlomki:
im not using exchange and it has happened to me with one of the roms.

the chef didn't really know what do with it or what's causing it, all i know is that it has never happened to me before, and after changing to shep's rom it hadn't happen since.

give shep's rom a try.
[Touch Pro, Fuze ROM Development] mattyman:
I'd think your Exchange server is having issues. There should be logs to see if a remote wipe was ever performed on your device. Are you sure your kids or annoying friends didn't try to unlock your phone a few times which may have caused the remote wipe?
[Touch Pro, Fuze ROM Development] Captain_Throwback:
This just happened to me on Sunday, running my own-cooked 23033 ROM (and about a week earlier as well)

I hadn't even tried inputting a password - my phone had been locked, and when I looked at it, I got the message about having one more chance to enter the password (which it wouldn't let me do - the phone was completely locked up). Since this had happened to me before (I had JUST finished putting most of the stuff back on my 16GB microSDHC card), I quickly removed the card, put in the correct password, and watched my phone hard reset.

So no, you're not crazy. It may be related to Exchange, but I doubt it. I think it's more related to Pin Lock, because after 5 unsuccessful attempts to unlock a device (whether it's synched with Exchange or not I believe), the phone is supposed to hard reset to protect your personal data. There must be a glitch with Pin Lock in some of the 6.5 builds that causes this on occasion. I'm not sure what it is, though.
[Touch Pro, Fuze ROM Development] hilaireg:
Did a bit of research ...

Apparently, a trusted application can initiate an erase-and-format operation by calling a LoadLibrary function in Fatutil.dll. There a registry key that controls full device erasure is:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\<MyProfileName>\FATFS]
"SecureWipe"=dword:1

Also, there is this key which controls LocalWipe and RemoteWipe based on the Password Required Policy (4131) setting.

[HKEY_LOCAL_MACHINE\Comm\Security\Policy\LASSD\DeviceWipeThreshold]
"4146"=1 through 4294967295 (0xFFFFFFFF)

4146 = SECPOLICY_LASS_DESKTOP_QUICK_CONNECT

Apparently, setting "4146" to zero (0) or 4294967295 (0xFFFFFFFF) disables the feature.

This is really going to suck if it turns out that some ROM packages now include LocalWipe/RemoteWipe as some form of anti cross-porting device protection.

HTH,
[Touch Pro, Fuze ROM Development] schwags:
Well that's good, i was starting to feel crazy. Exact same symptoms though, phone is just sitting there, locked, and when i turn the screen off I get that message. Most of the time the screen appears to be locked at this point, i'll try a reset and it boots, wipes instantly, reboots and runs through hard reset. I am preparing to install a few Exchange updates, so we'll see if that corrects it. I did check and our last major update was in April, and this started happening in late June, so I don't think it's Exchange either.

Thanks for that! If someone could be so kind as to whip that into a cab file, that would be great. Might at least give a temporary fix for this until it's figured out. I keep re-flashing new ROM's and hoping it'll go away one of these times.
[Touch Pro, Fuze ROM Development] dwmackay:
I would bet that the suggestion of remote wiping is the best track to follow. Perhaps the "Managed Programs" feature is somehow automatically set in your exchange environment and creating the problem? Although I do not know what I am talking about, just guessing. Seems like a security issue with your exchange/phone set-up. Try replicating the issue with the radio off. At least then you will know if it is an Over The Air Issue or something set on the phone itself.

Sounds like a real pain. Good luck sorting it out.

Doug M.
[Touch Pro, Fuze ROM Development] hilaireg:
Before putting together any form of .CAB, it would be worthwhile for those experiencing the problem to provide the following feedback:

Is it only occurring on devices receiving policies from an Exchange Server

Are the registry entries I noted above present and what are their values

Is the issue specific to certain ROM builds

Is there perhaps a common set of packages in use

Cheers,
[Touch Pro, Fuze ROM Development] NotATreoFan:
This issue was reported with my 23034 ROM by a user who syncs with Exchange. I do not sync with Exchange, and my unmodified ROM does not contain the DeviceWipeThreshold key.
[Touch Pro, Fuze ROM Development] Farmer Ted:
There's a thread started by a poster named zimo in the General forum that describes the same issue-I'd link to it except I'm on my fuze. It's several months old, and was just bumped.
[Touch Pro, Fuze ROM Development] hilaireg:
Appreciate the input; any other folks experiencing this issue and

are not

receiving policies from an Exchange Server?

Cheers,
[Touch Pro, Fuze ROM Development] Captain_Throwback:
I am synchronizing with an Exchange server, which enforces Security Policy on my device.

The first registry entry you noted is not on my device ("SecureWipe"), however the 2nd one ("DeviceWipeThreshold") is, and its value is set to "5" (which I believe means after 5 incorrect password attempts, the Device will wipe all data). It would appear that it's the Exchange server Security Policy that creates this key. So, I'd imagine changing this key might prevent Exchange from sychronizing (or it may just change it back by itself). That's something I can test.

I had this happen to me a while back, even before I was using 6.5; however the issue has become more frequent using 6.5. It may be because of changes to the Lockscreen, perhaps, along with a conflicting package that locks up the device, and makes it think buttons are being pressed or something. I'm not really sure on that one. The last build it occurred on was 23033/4 (I'm not sure which - I flash several times a day anymore). I did notice that on the 23034 build, when I would go to unlock my device, somehow a character was being input before I was even pressing anything, which I then had to delete to enter my PIN.

As you know, I have a whole slew of packages, but I generally use the same few in my ROMs, so if it was a package, I'd think this would happen to me on every build.
[Touch Pro, Fuze ROM Development] hilaireg:
@T-Back:

Changing the value won't make a difference as the Exchange Server policy push will reset the value - GPO's take precedence.
[Touch Pro, Fuze ROM Development] :
I use Zenyees Unlock. You might try it.
[Touch Pro, Fuze ROM Development] shlomki:
i am not using exchange server at all,

i do not lock my device in any way

and do not set any password.

this has happened to me 3 times in 24 hours using this rom, Build 23016:

http://xdaforums.com/showthread.php?t=540444

using shep's rom (build 23007) this does not happen to me at all, and i've been using this rom for a month.
[Touch Pro, Fuze ROM Development] hilaireg:
I was hoping it could have been an Exchange Server adjustment; but it's looking like it's not Exchange Server specific.

After reading the last set of posts, seems like some further investigation is going to be required to try and isolate the cause and implement a fix.

Cheers,
[Touch Pro, Fuze ROM Development] d96mbe:
The problem seems to be related to Exchange sync if the server enforces policies including remote wipe. I've experienced the problem at least 10 times on different roms since I switched to 6.5. My experience is that the problem has happened while using Tomtom.. However I'm pretty sure that Tomtom is not the root cause... It just might be that when using such applications you make sure that the screen is not locked for a long time. I'm using Zenyees Unlock to change the lockout timer from a maximum of 10 minutes to 40. This seems to reduce the amount of hardresets with wipes.

Another idea has to do with the storage card. But that is just a hunch.

Best of luck in solving this extremely annoying problem

/ M
[Touch Pro, Fuze ROM Development] shlomki:
@d96mbe, do you mind trying a rom that it's build is less than 23016?
[Touch Pro, Fuze ROM Development] tngbburg:
Same thing for me.

I've have had this issue on my Fuze, and my Tilt. I see it happen a lot on TPC's roms on both devices with windows 6.5. From the time wm65 showed up until now its happened on my devices. I have been using a app called "Stay Unlock" to override the exchange security policy to keep my device from locking. Even still on occasion when I plug my device into a pc and it wants you to unlock it it gets stuck and then wipes the device. I know now to make sure I yank my SD card because its a real pain putting all that stuff back on there. The problem only showed up when my company started enforcing security policy's on my devices. I had sync'd with exchange 2003 for several years, but after exchange 2007 and mobile security policies is when the problem started happening. With the stay Unlock program i only have it happen every once in awhile. I usually flash more than I have this problem so it doesnt' bug me too much. Plus since I sync with exchange all my stuff is there and I just resetup my exchange server and get all my stuff back. Then on my SD card I have all my custom cab's in a folder and just install real quick and I'm back to where I like to be.
[Touch Pro, Fuze ROM Development] hshortt:
Had this issue again this morning using NATF's 5.5 Series for TP. Again, no obivious indicator, device was sitting flat on the table, and when I turned it on it showed the '1 attempt remaining before reset', I pulled the micro SD and then entered the pin, my data was not erased this time.

Cheers
[Touch Pro, Fuze ROM Development] schwags:
Every once and a while i get lucky like that and it does let me enter the password.
[Touch Pro, Fuze ROM Development] hshortt:
Some additional information. This happens in a low signal area. This could be a vital clue in my opinion. I had the band set to automatic and it was on a HSDPA band, but with poor signal. Last night I switched to manual and selected just GSM. Now in the same place at work, I've much better signal - 3Bars, and have not had the issue yet.....today.

We'll see.

In relation to the signal strength, I am suggesting something along the lines of an attempted exchange policy refresh in a low signal area, the refresh fails and increases the pin attempts each time.

Just a theory.

Cheers
[Touch Pro, Fuze ROM Development] schwags:
Not trying to shoot down your theory or anything, but I've had this happen at my friends house multiple times where I have a minimum of two bars (usually 3-4 guaranteed) of HSDPA. I'm not sure that signal is related. It's a good thought though...
[Touch Pro, Fuze ROM Development] prag16:
I too am experiencing this problem. It was happening to me often in May/June and I finally got fed up and went back to WM 6.1.

I installed a newer build just yesterday of 6.5 and I had this problem within 24 hours; to make matters worse I forgot to pull the SD card because it had been a couple months since I'd used 6.5.

When it happened to me in the past, I was usually able to prevent the wipe by immediately soft resetting the device (after pulling SD card, then putting in a1b2c3, then OWA recovery password). But not this time! When I soft reset the device, it came back up in the hard reset sequence.

This is maddeningly frustrating. It has happened to me with several different 6.5 ROMS, the latest is the current RRE release. On RRE 6.1 ROMS, this problem never occurred.

The Stay Unlock type apps don't work for me... They work for a little while, but every hour or two the Exchange server re-asserts the policy, and I have to choose a PIN, etc. I can then rerun the unlock program, but now i'm doing this several times per day, and even better, a couple times between the time the policy was reasserted, and my rerunning of the Unlock tool, the problem happened...

arrupenthal thinks it is a bug with Microsoft's lockscreen files, and I have to agree based on the behavior and after reading this thread. Don't see how it can have much of anything to do with the Exchange server. Hopefully they'll have final files soon...
[Touch Pro, Fuze ROM Development] anit77:
I am a complete noob :o and probably don't know what I'm talking about but from the outside looking in it seems to me that for what ever reason when the phone locks in 6.5 it disconnects from the server at which point the server still sees the phone and attempts to reconnect in rapid succession. The warning about having one more password attempt is what freezes the loop.

Is there a way for you to follow the connection or look at the log files on the server to see times for the password attempts? If so you can compare them to a 6.1 rom from initial connection till the phone locks.

**Edit** It's most likely the opposite. When the phone locks the server disconnect it and the phone is trying to reconnect. It's still the warning that stops the loop and the log files should record the event. Especially if you increase the number of attempts and it still max's out in a couple seconds.
[Touch Pro, Fuze ROM Development] Jon Segger:
I've had it happen twice - but since then I've changed my unlock display to use 'Windows Classic' instead of 'Windows Default' and its not happened again...
[G1 Q&A, Help & Troubleshooting] jedinyt:
I have a Kingston 8Gig Class 4 and i just bought a Transcend 8Gig Class 6 SDCard.

Can someone please tell me step by step how to backup my class 4 to and restore it to my new Class 6.

Thanks in advance!
[G1 Q&A, Help & Troubleshooting] pistol4413:
ubuntu is the easiest way believe it or not as it is the only o that will see ur partition when u mount ur sd card. check out the wubi installer. or u can use adb.

adb remount

adb pull system/sd/app to pull the apps off, just replace pull with push when u want to put them back on the ext.
[G1 Q&A, Help & Troubleshooting] david1171:
i can't recall the exact thread in this Q&A section but there was one that showed how to backup /system/sd to your sdcard then you could pull those files off on a computer and put them on the new sdcard then copy them back over to the second partition.

i think they were something like

mkdir sdcard/ext2 (the directory name doesn't matter just whatever is easiest for you to remember)
cp /system/sd /sdcard/ext2

someone correct me if something is wrong with those. then put those files on your new sdcard and go to the recovery console so you won't have to worry about any force closes with the new sdcard. make sure you do this after partitioning your new sdcard

mount /system
mount /sdcard
mkdir /system/sd
cp /sdcard/ext2 /system/sd

i think the commands were something like that. but if you have adb then the way posted above is the easiest for me.
[G1 Q&A, Help & Troubleshooting] shaolinx:
Why don't you just use backup(for root) users application? just copy the folder it creates on your sdcard to your drive, and place into the new sdcard.
[G1 Q&A, Help & Troubleshooting] AdrianK:
@David, I think those commands would work, but here's what I always do (and can verify it works).

rm -r /system/sd/dalvik-cache/*
rm -r /system/sd/app_s/*
cd sdcard
mkdir ext
cp /system/sd/* /sdcard/ext/

Then to push back

mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*
cp /sdcard/ext/* /system/sd/
reboot

Its best to do all that in the recovery console, or adb shell when the phone is in recovery. Don't do it while the phone has booted in the ROM.
[G1 Q&A, Help & Troubleshooting] jedinyt:
Thanks for all the help/reply...

one more question... how do i do it? do i do it in the terminal? console? or adb?
[G1 Q&A, Help & Troubleshooting] supremeteam256:
What they just gave you would be done in terminal.
[G1 Q&A, Help & Troubleshooting] AdrianK:
I said at the bottom of my post. Recovery console is best, if you do it when your phone is actually running you could have issues.
[G1 Q&A, Help & Troubleshooting] random_username_:
or adb shell
[G1 Q&A, Help & Troubleshooting] AdrianK:
Well yeah, ideally when the phone is in recovery...
[G1 Q&A, Help & Troubleshooting] sugar0:
i have a Desire and im wondering if there's a easier way to clone the sd card to another bigger. Any idea ? Cloning softwares ?
[G1 Q&A, Help & Troubleshooting] deckoff:
What about just dd the SD card. something like:

1. Turn off the phone

2. dd sd card to img file

3. dd img to new file

4. New sd in slot and reboot
[Tilt, TyTN II, MDA Vario III General] dowmace:
I'm trying to flash a hardspl but everytime I have the phone plugged in everything is going ok but it will go into the progress bar, sit at 0% for about 5 mins then give me a 262 communication error. What the heck anyone got any advice? Thanks in advance guys.
[Tilt, TyTN II, MDA Vario III General] DaveTheTytnIIGuy:
You followed the noobs guide exactly, right? Because when I experience communications problems, 99% of the time it's because I didn't pull out my SIM and SD cards.

Dave
[Tilt, TyTN II, MDA Vario III General] dowmace:
I did in fact follow it exactly. I just hard reset the phone and tried the exact steps again worked this time, I guess I just didn't have the cord plugged in right or something, or maybe it was luck I don't know!
[G1 Q&A, Help & Troubleshooting] Brandice128:
Hi I was just wondering how do you use java? Like how do you get the apks from the SD card using java? It doesn't wanna work for me, any idea? :confused:
[G1 Q&A, Help & Troubleshooting] grandomegabosses:
you don't use apk files for java. .jar files are what you want.
[G1 Q&A, Help & Troubleshooting] Brandice128:
Where can I get the .jar files?