Leaked DL30 Froyo Build Available NOW! (Includes Full Instructions: Updated 2/5)

[Sta11i0n]

No sir. Someone steal my name?

 

[DroidXcon]

Cool then I guess this is worth a try also. I just could never get ODIN to see me if I didn't hold the button as I plugged in. Probably user error.

Odin is really finiky about its connection, it could be your computer....

from being on here and enough stories here are things that effect Odin

Laptops> Laptops are designed to change voltage to conserve when it can so if you are going to use a laptop for odin you need to make sure that it is plugged in and you are not running any other processes.. they are pretty bad for flashing odin

Anti-virus> for some reason it interupts your usb connections, i dont know why i could even be wrong but many cases i have walked through disabling anti-virus will ensure you wont get hung up in the middle of a flash

Remote ports> internal remote ports(USB in front of PC), monitor ports, hubs . are all very bad for trying to connect to Odin since they are usually connected by a long cord there is a signal drop and you will either lose connection to odin in the middle of a process or not be able to connect at all.

Manufacturer specific USB cable> different manufactures Ground their cables differently resulting in not so great results when not using manufacturer USB cable


After market USB Cable> length is also a problem, when using after market USB cables make them short as possible ,,, Also grounding problem can be seen in generic cables as they are not samsung specific

USB ports> there are powered and non powered USB ports so this will effect the load voltage... for me non powered work the best as it gives a steady signal sometimes you will need to use the battery in but this is rare and i dont recommend it... alot of people get hung up in the middle when having the battery in and also after you boot back up it trys to load the phone and in some cases this is less then helpful.

Drivers> obviously its been seen time and time again that not having the proper samsung drivers can cause you a headache

IDEAL SITUATION>Using Ports in the back of the desktop computer closest to the board with the manufacturers cable.......reason desktop is best because the voltage is regulated and steady unlike a laptop that does not have a huge powersupply....using ports in the back are usually connected to the motherboard there for there is less signal drop providing ideal connection. but even then a bad solder joint could cause a bad connection so try different ports.

 

[Landshark]

No sir. Someone steal my name?

Steal your name? Say it ain't so. That name is so awesome you should get royalties if someone else uses it.

 

[kdfdawg]

question -- how long should it take to wipe/clear the cache from recovery mode... trying to fix the force close issue i'm having

 

[Sta11i0n]

Under 30 seconds.

 

[kdfdawg]

Under 30 seconds.

oh boy.. it's been stuck wiping cache for over 5 minutes... what do i do now??

 

[Sta11i0n]

What does it say right now?

 

[DroidXcon]

you can do a battery pull,,,,, try to wipe dalvik cache, see if that help the problem or if it persists,,, are you using red or green clockwork?

 

[kdfdawg]

What does it say right now?

it just says wiping cache... and it's been stuck in this state for a while now.

 

[kdfdawg]

you can do a battery pull,,,,, try to wipe dalvik cache, see if that help the problem or if it persists,,, are you using red or green clockwork?

i used the red clockwork i believe.. whatever was said in the first post.. i followed those directions and ended up with the force close issue. i've never flashed a rom before, so i'm new to all this

 

[Sta11i0n]

Sounds like it never really started then. I get that sometimes when trying to make backups. Like X said, pull battery. Try wiping dalvik cache, cache partition, and fixing permissions before losing all your data.

 

[DroidXcon]

Mind you after wiping dalvik you may end up booting into safe mode and getting an error, if this happens , reboot hopefully error will be gone

 

[kdfdawg]

Sounds like it never really started then. I get that sometimes when trying to make backups. Like X said, pull battery. Try wiping dalvik cache, cache partition, and fixing permissions before losing all your data.

sorry to sound so noobish --- but how do i do all the things you just mentioned?

sorry

 

[Sta11i0n]

They're in CWM Recovery in the "Advanced" section. Also don't freak out when you restart and it sits at the verizon screen for a few mins.

 

[DroidXcon]

scroll down to advanced , select it and it will give you those options

 

[kdfdawg]

i tried wipe dalvik cache - and it's saying

CwM Voodoo Lagfix Recovery v2.5.1.x
E:Can't mount /dev/block/mmcblk0p1

 

[Sheepdog Elite]

i tried wipe dalvik cache - and it's saying

CwM Voodoo Lagfix Recovery v2.5.1.x
E:Can't mount /dev/block/mmcblk0p1

Got the same error trying to wipe battery stats from red. New green did it fine.

Red CWM will not make a back up on DL30 from what i've been able to figure out. Red seems to be turning into a trouble maker in general.

 

[DroidXcon]

i tried wipe dalvik cache - and it's saying

CwM Voodoo Lagfix Recovery v2.5.1.x
E:Can't mount /dev/block/mmcblk0p1

i get that, then it wipes anyway

 

[kdfdawg]

okay --- after getting that error when running wipe dalvik cache, i went back and wiped cache partition and fixed permissions and rebooted .. still force close issues...

ugh...

 

[DroidXcon]

okay --- after getting that error when running wipe dalvik cache, i went back and wiped cache partition and fixed permissions and rebooted .. still force close issues...

ugh...

ok try all this once more, cache partition, dalvik , wipe data, fix permissions,,,,,,,,then flash DL30 again