yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] sgt. slaughter:
Yes agreed. This is what I said in response to that post the first time. I was just bringing it back up b/c the poster seemed like they were sure unrevoked unlocked NAND which is NOT the case. Hence you run some Roms and will have issues if your not fully root.
[EVO 4G General] SilverZero:
And doesn't Unrevoked unlock NAND but only while it's rooting/running? I believe I saw that somewhere as well.
[EVO 4G General] sgt. slaughter:
Got me, once I read of it messing up some peoples 4G awhile ago and some phones I didn't bother with it. I'd rather do it the hard way and know exactly what I'm doing to the phone rather than a program that there is little detail out there on what all it exactly does and how it does it.
[EVO 4G General] SolsticeZero:
You'll never catch me doing Unrevoked. I mean, it's really not that much harder to root a phone the real way (through Toast's method).
[EVO 4G General] davejet:
Thanks for all the info. I am confused though if Unrevoked 3 was used and then simple root .2 wouldnt simple root give full root and nand unlock??
[EVO 4G General] sgt. slaughter:
yes as long as you FULLY get through ALL the steps. untill the poster can reply back in the WIP thread to the question asked we cant do much more on this.

My comments were directly against the statement that unrevoked did a full root b/c thats not the case at all.

there is another WIP thread in the Dev section working on a theory around getting PRI to stay but they need a non rooted phone to try the process out on first.
[EVO 4G General] TheBiles:
Can't say we didn't warn you.
[EVO 4G General] ISSMER:
I am willing to give it a shot...I am not rooted...running 2.1 update 1...software version 1.47.651.1...PRI 1.40_003
[EVO 4G General] adeyo:
FIX FOUND in another thread

So did replicating the steps work???

--------------------------------------------------------------------------

EDIT: seems they were "mistaken" ....IGNORE BELOW

Keeping the PRI 1.40 for those who have not rooted yet was solved about 10 minutes ago and confirmed... http://xdaforums.com/showthread.php?t=748021 So no need for unrevoked root to do so (if this was really cracked)...now they are working on a way to fix the downgraded pri w/ a zip somehow. who knows how long it will take for that though.
[EVO 4G General] ISSMER:
!!!!SWEET!!!!

Any chance an updated PRI will be released by Sprint at some point in the future? How will the update to it work? I assume the same update image and flash process would apply.
[Android Software Development] shanesurk500:
Hi. Im new and im having some compatibility issues with the Android SDK. I open it up, and the window that opens closes out immediately. On its own. I troubleshoot compatibility with Windows' assistance, but i havent received the results of the error report i submitted, and windows wouldnt tell me which program it was incompatible with. Any help would be GREATLY appreciated. Thanks.
[EVO 4G Q&A, Help & Troubleshooting] Alanmw86:
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.

I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.

Any idea's?

I'm entirely stumped.
[EVO 4G Q&A, Help & Troubleshooting] cervantes008:
Start over

Nand recovery then root again. Find a stable rom. There are tons that float to the top of the forum. I'm on Damage Control 3.5, works great.
[EVO 4G Q&A, Help & Troubleshooting] Alanmw86:
Tried to Nand, It error's out and won't restore.

Like I said, DC 3.5 is what gave me the trouble to begin with, at least thats when my troubles started.

My phones gone completely unstable..and at the moment, unusable.
[EVO 4G Q&A, Help & Troubleshooting] cervantes008:
Also, be patient. After a flash, it may take a while for it to load. You seem overly anxious, by your post. I've flashed 30x and probably only bootlooped twice and those were Fresh's 3rd to last rom.
[EVO 4G Q&A, Help & Troubleshooting] Alanmw86:
I let it sit there for 10 minutes saying fresh 1000x over a couple times, pretty sure I'm not being impatient.

battery is now dead.
[EVO 4G Q&A, Help & Troubleshooting] cervantes008:
Full wipe

Are you wiping everything? Dalvik wipe, user data wipe, cache wipe? Can you get back to recovery? How did you root?
[EVO 4G Q&A, Help & Troubleshooting] Alanmw86:
Yes I can get into recovery, yes I'm wiping everything.

I used Simpleroot to get Root.
[EVO 4G Q&A, Help & Troubleshooting] cervantes008:
Rerun

I would try to re-run the second button in simple root to unlock nand. It doesn't hurt to re-run. You really shouldn't have a problem recovering nand if that process worked the first time. If you can't get that to run, you might want to adb it, but since you simplerooted your phone, you might have to read up on that. Once you take care of nandroid, you are good to go.
[EVO 4G Q&A, Help & Troubleshooting] Alanmw86:
Nand is giving me an error that backup cannot be found <even tho I most definitely did Nand backup my stable setup> so IDK what fixing nand would do even if it is broken if it cant find the restore files. erm..
[EVO 4G Q&A, Help & Troubleshooting] cervantes008:
End of the Road

I suggest you do a forum search for more opinions/solutions. You are not the only one on here that has been through this. I did a quick search and found a handful of threads with this exact same topic.
[EVO 4G Q&A, Help & Troubleshooting] n1gh7m4r3:
How did you install a different recovery if your stuck in a boot loop? As for your problem, i had a bootloop before on freshz's older rom, and some of the solutions i had read werent working, i ended up booting into recovery, and rewiping without doing a reinstall of the rom, and it solved my problem, also have read that pulling the battery has gotten some people out of there loops. Hope this helps
[EVO 4G Q&A, Help & Troubleshooting] Alanmw86:
I pulled the battery booted into recovery and wiped the rom, flash an alternate, booted up, changed to Amon and started over, was the one time I was able to get it to boot threw, after that same results.. I couldn't explain how it managed to boot up just one time either.
[Desire Q&A, Help & Troubleshooting] joe2316:
Has anyone else noticed the sensitivity change from Eclair (stock T-Mobile) to Froyo (DeFrost 2.5a)?

It requires much more screen contact now.

Anyone else?
[Desire Q&A, Help & Troubleshooting] timmmah.l:
Honestly when I had the OTA update to froyo with sense, didnt notice any difference, however once I rooted and installed DeFrost, I did have a feeling touch wasn't as sensitive........ But simply thought I was going cuckoo, I'm already use to it!
[Desire Q&A, Help & Troubleshooting] millab:
I certainly haven't seen this problem on my desire, my screen is still so sensitive that i don't even need to touch the screen (i can hover 1mm away and it registers a click)
[Desire General] mmaacc:
Tons of new ROMs coming out now based on OTA and adding A2SD+. But one big issue. Quite a number of people have reported problems with corruption of their SD cards when setting the Desire into Disk mode and connecting it to a PC. I've read it the first time here

http://xdaforums.com/showpost.php?p=7463184&postcount=348

and I can confirm it is reproducible.

Regardless if connecting to Windows or Linux, the card gets corrupted. It does not matter if you properly eject the drive. The Desire will respond saying the SD card is Read Only, and the only thing that one can do is to repartition it to fix the card.

I don't know what A2SD+ application everyone uses in their ROMs but I expect it's all based on some common version like the one put in from ieftm. As this is a serious issue it would be great if all you ROM cooks could look into it and try to fix it. Alternatively it may be a good idea to produce non-deodexed versions that save a significant amount of memory when installed normally without A2SD+.

Thanks for considering :)
[Desire General] audipete:
I have this problem aswell its a bit of a nightmare there are a few files on my sd card that I can't even delete using andexplorer or my pc. I think the only way would be to remove my card and format it. I have never had this problem before only when I started using the 2.2 rom.
[Desire General] madd0g:
Noticed it before, i took the SD card out and put it into a cardreader, couldnt do anything in windows, said it was read only. Access via USB cable worked though.

Not that much of a issue for me, I mainly transfer files via Wi-Fi anyway, but I guess thats the explanation for the read-only behaviour.
[Desire General] .:george:.:
Happened to me today, however I restarted the phone and everything seems okay now... :/

edit: nope, connected the phone again, chose "charge only" and then disconnected. The notification about my card being corrupted occured again, tapped on it and it went away... Dont know what to think.. :(
[Desire General] uncleslim:
I have the same problem .. And now it seems like the SD card is totally corrupted. Its not even possible to do a format:eek:
[Desire General] .:george:.:
Okay thats it... Doing the titanium backup, nand backup and flashing some rom w/o A2SD+... :/
[Desire General] DuneBug:
Out of curiosity guys, did the corruption of the SD card occur to the stock SD card that came with the Desire? I had the same problem with the stock card..

It seemed to unmount 3 or 3 times over a week and the next thing I knew it totally died and could not even be reformatted.. Happened on stock 2.1 that came with my Desire.. after I swapped to me own class 6 8gb Transcend I never had the proble again.. Just gonna upgrade to 2.2 now.. *fingers crossed*

Oh and yes.. I use A2SD+ on Modaco's 3.1. But that was after that card got corrupted..
[Desire General] .:george:.:
I'm using card that came with the phone.

I'm going to try another Froyo Rom, just OTA rom rooted and we'll see.

Edit: I made my ext3 partition with ROM manager, if it makes any difference...
[Desire General] .:george:.:
God dammit!

http://xdaforums.com/showthread.php?t=747480
[Desire General] uncleslim:
Yes its the card that came with the phone .. but it happen after i created the 512MB EXT3 Partition ... and I'm running this ROM : http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=741775&highlight=official it doesnt even use A2SD+ :confused:
[Desire General] LeeDroid:
I dual boot my pc with windows 7 & ubuntu.... windows 7 scan and fix has repaired mine numerous times
[Desire General] pinkolin:
I have class6 A-DATA 8GB and no problem. But with my last G1 i haved same card and with swapping goes to hell... I now correctly unmounting and disconnecting mobile from PC, after i save from PC to card. Flash have problems with writing.
[Desire General] lordlaurin:
This looks like a serious problem - it happened to me twice already. :( Devs, please have a look at this!
[Desire General] delta-101:
I have also had similar experience, SD card corrupt, yes it was the original card that came with the phone, EXT2 partitioned and using APSD+

Now why this happend is a mystery, but something I noticed when I tried the SD card in the PC - it was recognized, but said it must be formated, so I tried but it only saw it as a 32mb capacity!!! (it still would not format though - failed format..and since is no longer reconized at all..)

But, this made me think it "MAY" be something to do with the fact that when I did the Ext2 partition I seem to remember it also created a 32mb swap partition, or using Ext2 instead of Ext3. I have since learnt that it is advisable NOT to created a swap partition, so with my new SD card, after more reading about Ext partitions etc, I have only created only the Ext3 partion as I understand this is better than Ext2 and is less prone to corruption, and no swap partition and have had no problem since!

See this excellent post :- http://xdaforums.com/showpost.php?p=7458565&postcount=8

It would be interesting to have some input from one or two of the developers with knowledge in this field to get an idea why this happens, and how it can be prevented.

It is also possible the the SD card was going to become corrupt anyway... with or without the help of Ext? / APSD+ - it does happen!
[Desire General] KuRouZu:
my sd was corrupt using a 512MB ext3 partition without swap partition in SD card :/
[Desire General] twicejr:
Try in windows: start > run > chkdsk x: /f

where x = desire drive letter.

I believe i did this in recovery mode > mount usb.
[Desire General] beidl:
That's what happens when you don't want to use Froyos own A2SD implementetion because "widgetz doesnt workzz on dat."

Apps are not meant to be on an external EXT partition.

Wait until ROMs like CM have built in A2SD+, these hacky shell scripts can cause serious problems for the SD card.
[Desire General] mmaacc:
Windows can not access EXTx partitions. As such is unfortunately not possible that it could possibly repair a broken SD-ext partition A2SD+ uses.
[Desire General] KriXou:
I can confirm the corruption without any APSD+ ROM

I had a Stock Orange FR 2.1 ROM, and the 4Gb card that came with the phone get corrupted definitively (recognized as a 32mb capacity too, it has something to do with the Cylinder-head-sector combination).

Anyway, I'm going to try APSD+ with a class 2 PNY 16Gb, and tell you then if I get a corrupted card.

FYI, the Sandisk warranty is applicable for the original card: replaced in 5 days
[Desire General] Madeli:
I got some problems too with corruped files on my SDcard and had to format it. I'm thinking that from now i'll only mount my card to pc in recoverymode... maybe that is safe to do?
[Desire General] dezborders:
Has anyone worked out why this corruption has only started happening since the official HTC Froyo ROM was released last weekend?

As far as I know, no other Froyo rooted ROMs have ever exposed this issue, not even the leaked HK test HTC Froyo ROM in July...

I so far have NOT experienced the problem - touch wood - despite using ext3 and A2SD+
[Desire General] DuneBug:
Well as far as I'm concerned, my corruption occured a long time back (may?).. I think it has nothing to do with the update.. my suspision is a faulty batch of Sandisk 4gb cards.. I had the same problem where windows AND linux reports 32mb card and unable to restore to capacity regardless of ANY formatting or Partition recovery tools used..

For the record, my corruption occured about 2 weeks after I got the phone..
[Desire General] mmaacc:
Kingston 4GB card here, 512MB EXT4 got corrupted. Has nothing to do with a particular batch. And it only gets corrupted if you create an EXTx partition and mount it as drive. Normal single FAT partition is not affected.
[Desire General] jorgenask:
anyone found a way around this problem . I am having this issue now with this ROM :

[ROM] Official 2.2, with: busybox, old A2SD+, OpenVPN (TUN), EXT4 support, 802.11N

have a 8GB class 2 sdcard . dont remember if its sandisk or kingston.

anyone know if there is problems with class 4 and 6 as well ?
[Desire General] TieT:
same problem here !

using a 8Gb sd with 512mb ext 3 partition,

The card will get corrupt after connecting it thru usb modus.

Some files cant be deleted, card is read only, etc etc

Ive had this problem over 3 times now !

im using

[ROM-FroYo] Official Froyo HTC Sense ROM (16/07 v1.0c | OpenDesire Team)
[Desire General] jorgenask:
bump :) bump :)
[Desire General] kuailan:
I really dont think it's because of the SD brand or class. I am currently using Kingston class 6. Because of this issue, I switch back to older EXT. Apparently, with the EXT, there is no corruption, except you will need to reboot for the files to be seen by your windows EXPLORER. It's not really a big deal, since your phone can also see the files using your phone.
[Desire General] jorgenask:
ahh ... it helped rebooting the phone ... can this be somewhat of a software bug somewhere ? ... after reboot ... i can see the pictures from my pc when connected via usb mass drive.

not actually sure wich ext version i have on my sdcard ... i just formatted it with amon ra recovery ... didnt change it to ext 3 or ext 4 or anything...
[Desire General] jorgenask:
have tried both "change file system from ex2 to ext3" and ex3 to ext4" ... no difference ... i assume amon ra doesnt use ext1 as it only says from 2 to 3 and from 3 to 4.

gonna try with kingston 16GB class 10 ... ordered some days ago. dont know if thats gonna make any difference.
[Desire General] DuneBug:
OK.. New Info!

Looks like they caught a bug over at Modaco:

I'll try to explain when and how the FAT32 partition is corrupted.

At least, the problem occurs with the 3 custom rom version I tested:

[Froyo Sense] LeeDrOiD Mod V1.8 (07/08 l Official HTC 2.2 l Fast l Stable! l A++)

[Rom](05/08/10) Alex-V 1.1 OTA Froyo Sense based on Paul (modaco) only added App2sd+

[ROM] Official 2.2, with: busybox, old A2SD+, OpenVPN (TUN), EXT4 support, 802.11N

http://android.modaco.com/content/h...at32-sd-partition-explanation-for-developers/
[Desire General] ninjaz:
Are you usinig HTC Sync 3? I have a same problem after sync with HTC Sync.
[Desire General] jorgenask:
anyone using a ROM vith a2sd+ that DONT have this problem ? and what is that ROM ?
[Desire General] camomilocamo:
same problem here

Sd card 16gb, class 6, no swap.

I think it happens when you are connected to computer and you change from your mode on desire to another mode of connecting with pc. For example, when you change from "hard disk" to "Only charge", but ALWAYS being connected to computer.

I probed so many roms, but never changed my connection to pc BEING CONNECTED TO PC, untill now !!! and that´s what happen, sd corruption...

What do you think about?

(sorry about my english.)
[Desire General] Egan:
I had this problem about 2 months ago when I still had MCR r4 installed, without A2SD(+) or EXT partition and stock SD. I didnt had fake-flash or a custom recovery then. I connected my Desire many times to the PC with USB in order to copy files or flash a ZIP. I often had a read-only SD and had to reboot to fix it. Suddenly my SD was corrupted and couldnt even be partitioned or formatted again.

After buying a new SD (SanDisk 16GB) I used the app SwiFTP (FTP server) to make the connection between my Desire and PC, used fake-flash and never seen the problem again.

Mounting SD to PC (in my experience) is asking for trouble, with or without A2SD, EXT, etc.
[Desire General] jorgenask:
Still hoping that someone can resolve this problem :)
[Desire General] jorgenask:
any news on this guys ? :)
[Desire General] mmaacc:
Might be interesting if there are differences between EXT2 and EXT3/4. EXT2 does not have journaling.

Anyway, I think an odexed ROM may be the best solution without eating too much memory and without using an ext partition.
[Desire General] dezborders:
I have first-released OTA 2.2 rooted/A2SD+ ROM (http://xdaforums.com/showthread.php?t=741663)

However, I always do (and always did, even on 2.1) put the handset into Airplane mode

before

activating Disk-drive Mode.

The idea behind this is to 'quiesce' the OS - i.e. stop as many apps as possible from trying to write to SD whilst the PC is accessing it in Disk-drive mode.

I have NEVER experienced SD corruption after disk mode or after Sync.
[Desire General] wency_99:
i agree with this assessment... just like any OS, when the OS is writing to any disk and you yank it out, it will get corrupted, regardless... so it is really better to do proper mounts and not just switch modes on-the-fly... this happened to me on a regular harddrive so this is nothing new in the computer world.
[Desire General] Gekx:
I would only mount your SD if your in Recovery mode. This has and probably always will be and issue for people using A2SD. Like others say it would be like disconnecting a hard drive from your computer while it was using it... you'll get corrupt files thus a corrupt SDcard.
[Desire General] mmaacc:
Here is something new I just discovered. The corruption is real, it is a problem caused by something in Froyo (it worked in 2.1) and it is triggered by some 3rd party tools that interfere with Froyo's internal mounting mechanisms.

That is not only A2SD+. I just figured out the exact same corruption happens with the Dual Mount SD widget (a small tool that lets you mount a SD in parallel to a PC and the phone). It worked for a short while, using my own A2SD+ free ROM and FAT32 only. Data did not show up on the card (that is in the file manager in the phone, it was still physically on the card and visible on the PC). I tried then to unmount/mount the SD FAT32 in the phone and voila, read only corruption as with A2SD+.

So, this is a more general Froyo problem we see here, A2SD+ is just one thing that triggers corruption, but it is not the root cause for it. Something has changed in Froyo itself compared to earlier versions and messes up with 3rd party mounting of the SD card.
[Desire General] sturm100:
Corruption? hmmm i guess im damn lucky, i have been using nextsense 5.3 till now 7.1 and had ext3 and never once encounter a corruption...only once i had file lost cos i pull out in a hurry while copying files to my sdcard.... my sd card is a 16GB and previously was a 8GB class 2 though...using ext3 formatted by using acronis disk director...i mount my card everyday in office and at home...copying and deleting files, apk, etc...even did an hour of transfering of files for the past 2 days and no corruption as stated..

however my usb connection is always on debug mode, and default connection is always charge only, and "ask me about usb connection type when i connect to pc" is checked...im on windows 7...
[Desire General] mmaacc:
This means you use adb only to access the SD in your phone. And you do not change the mounting regime of Froyo. If so that would confirm my theory. Something changed in Froyo that is incompatible with previous 3rd party mounting.
[Desire General] sturm100:
dun think so im using adb in my work place (please enlighten me if im wrong on how adb works)...my work place put a strong security policy that no software are allow to be installed, but i am still able use my phone as a removable disk to transfer files, and as i mentioned i see it as a removable drive, and did transfer huge amount of data across everyday on my home pc to backup my files on the sd card..

and google this issue and found that this problem has existed since 1.5,

they had this issue even on 2.1
[Desire General] sturm100:
I think I take back my words, after posting, my pc at work can't detect my card but my phone does, however all content is read only,

Sigh
[Desire General] mmaacc:
Told ya :).

If it's only your FAT32 that is read only just plug it into your PC with a card reader and do a chkdsk. Data should still be there. If it was an EXTn partition you need to repartition the card, it's likely beyond repair (at least it was for me).
[Desire General] cez10:
i think my card is corrupted in a different way.

when i connect it to the pc it reads everything etc, but when i try to transfer some files onto the sd it hangs and cannot safety remove it in windows, but surprisingly it lets me change from disk only to charge only in phone settings, then the card hangs as phone cant read the card and have to take it out and fix files in Windows using a card reader.

weird thing is it only happens with Windows 7, XP worked fine :S
[Desire General] Daelyn:
Using 2Gb ext4, 13.5Gb FAT32 and 0.5Gb Swap.. Not had a single issue yet. On the other hand, I reboot my phone quite often (WinMo habit), testing stuff, flashing radio's and other contents.

How about using a ADB push/pull Win shell extention instead? Saw someone in here had written one to use in Win. Could be a circumvention of the problem until it is sorted, whatever it may be.