yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] volwrath:
Dont put TOO much money on that bet as my problems (although slight) have occurred WITH md5sum check. I will state once again that after moving to v5, my phone 3G + voice has only died once.

---------- Post added at 10:39 AM ---------- Previous post was at 10:38 AM ----------

Hah yes I am honored to be part
[Samsung Epic 4G Touch] Fus3D:
What oc kernel? My eyes lit up when I read that, where is it at?
[Samsung Epic 4G Touch] xlGmanlx:
There currently are two rooted kernels in the development thread
[Samsung Epic 4G Touch] PhantomPhreak53:
http://xdaforums.com/showthread.php?t=1269437
[Samsung Epic 4G Touch] xlGmanlx:
http://xdaforums.com/showthread.php?t=1267762
[Samsung Epic 4G Touch] derrickonline:
Here's a thought

Add me to the list of people intermittently losing service.

But I should note I had flashed the kernel listed on the ACS site. I thought it was the same thing.

Now I'm flashing this (ZedoMax) kernel, I'll let you know if it works or I continue to intermittently lose service.

Is there anyone who flashed the Zedomax kernel, that has NOT experienced the intermittent "NO SERVICE" issue that's only corrected after a restart? I flashed the ACS kernel this morning, I'm on my 3rd restart to clear the signal issue. So if you've had the kernel flashed for 8 hrs or more and haven't had the the "NO SERVICE" issue you're probably good.

I just flashed this Zedomax kernel I'll let you know if it continues. Like me maybe there are people who confused the ACS and Zedomax kernel for being the same thing?
[Samsung Epic 4G Touch] xlGmanlx:
When reporting issues its probably best to mention if you are rooted or not
[Samsung Epic 4G Touch] volwrath:
The zedomax kernel is older than v5 acs.
[Samsung Epic 4G Touch] shabbypenguin:
i need someone to do these commands and paste the outputs for me.

adb shell ls -l /dev

and adb shell ls -l /dev/block

thanks :)
[Samsung Epic 4G Touch] datajosh:
adb shell ls -l /dev

opendir failed, Permission denied

adb shell ls -l /dev/block

brw------- root root 254, 4 2011-09-17 12:57 dm-4

brw------- root root 254, 3 2011-09-17 12:57 dm-3

brw------- root root 254, 2 2011-09-17 12:57 dm-2

brw------- root root 254, 1 2011-09-17 12:57 dm-1

brw------- root root 254, 0 2011-09-17 12:57 dm-0

drwxr-xr-x root root 2011-09-17 12:57 vold

brw------- root root 7, 7 2011-09-17 12:57 loop7

brw------- root root 7, 6 2011-09-17 12:57 loop6

brw------- root root 7, 5 2011-09-17 12:57 loop5

brw------- root root 7, 4 2011-09-17 12:57 loop4

brw------- root root 7, 3 2011-09-17 12:57 loop3

brw------- root root 7, 2 2011-09-17 12:57 loop2

brw------- root root 7, 1 2011-09-17 12:57 loop1

brw------- root root 7, 0 2011-09-17 12:57 loop0

brw------- root root 1, 15 2011-09-17 12:57 ram15

brw------- root root 1, 14 2011-09-17 12:57 ram14

brw------- root root 1, 13 2011-09-17 12:57 ram13

brw------- root root 1, 12 2011-09-17 12:57 ram12

brw------- root root 1, 11 2011-09-17 12:57 ram11

brw------- root root 1, 10 2011-09-17 12:57 ram10

brw------- root root 1, 9 2011-09-17 12:57 ram9

brw------- root root 1, 8 2011-09-17 12:57 ram8

brw------- root root 1, 7 2011-09-17 12:57 ram7

brw------- root root 1, 6 2011-09-17 12:57 ram6

brw------- root root 1, 5 2011-09-17 12:57 ram5

brw------- root root 1, 4 2011-09-17 12:57 ram4

brw------- root root 1, 3 2011-09-17 12:57 ram3

brw------- root root 1, 2 2011-09-17 12:57 ram2

brw------- root root 1, 1 2011-09-17 12:57 ram1

brw------- root root 1, 0 2011-09-17 12:57 ram0

brw------- root root 253, 3 2011-09-17 12:57 cyasblkdevblk0p3

brw------- root root 253, 2 2011-09-17 12:57 cyasblkdevblk0p2

brw------- root root 253, 1 2011-09-17 12:57 cyasblkdevblk0p1

brw------- root root 253, 0 2011-09-17 12:57 cyasblkdevblk0

brw------- root root 179, 12 2011-09-17 12:57 mmcblk0p12

brw------- root root 179, 11 2011-09-17 12:57 mmcblk0p11

brw------- root root 179, 10 2011-09-17 12:57 mmcblk0p10

brw------- root root 179, 9 2011-09-17 12:57 mmcblk0p9

brw------- root root 179, 8 2011-09-17 12:57 mmcblk0p8

brw------- root root 179, 7 2011-09-17 12:57 mmcblk0p7

brw------- root root 179, 6 2011-09-17 12:57 mmcblk0p6

brw------- root root 179, 5 2011-09-17 12:57 mmcblk0p5

brw------- root root 179, 4 2011-09-17 12:57 mmcblk0p4

brw------- root root 179, 3 2011-09-17 12:57 mmcblk0p3

brw------- root root 179, 2 2011-09-17 12:57 mmcblk0p2

brw------- root root 179, 1 2011-09-17 12:57 mmcblk0p1

drwxr-xr-x root root 2011-09-17 12:57 platform

brw------- root root 179, 0 2011-09-17 12:57 mmcblk0
[Samsung Epic 4G Touch] shabbypenguin:
OH SNAP. no more bml's eh? mind doing ls -l of platform in there as well :)

thanks
[Samsung Epic 4G Touch] datajosh:
Yeah I was wondering if the bmls weren't there or if I just needed root to see them. (I'm assuming it's the latter myself.)

adb shell ls -l /dev/block/platform

drwxr-xr-x root root 2011-09-17 13:01 s3c-mshci.0

Edit: and here's the contents of s3c-mshci.0 if you need it although it looks like it all points to /dev/block

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p12 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p11 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p10 -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p9 -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p8 -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p7 -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p6 -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p5 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p4 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p3 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p2 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0p1 -> /dev/block/mmcblk0p1

drwxr-xr-x root root 2011-09-17 13:01 by-num

lrwxrwxrwx root root 2011-09-17 13:01 mmcblk0 -> /dev/block/mmcblk0
[Samsung Epic 4G Touch] Chainfire:
mmcblk's have replaced them.
[Samsung Epic 4G Touch] shabbypenguin:
alright cool, so i guess a good starting point is having someone with root (the sgs2 kernel) do a dd and pull all those mmcblk's

adb shell dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img

rinse and repeat with all the numbers. upload em so someone can look at them

anyone know if its zimage again, or did they finally switch to boot.img on a high end phone?

also to speed things up a bit

adb shell mounts

(dont need to be root to run that command)
[Samsung Epic 4G Touch] Chainfire:
On the (original) SGS2 it's zImage, and if I remember correctly they are mmcblk0p7 and 8. I'm not at my dev PC else I'd look it up. If needed I can remote in later and look at my files ...

Easy to figure because they'll be the only 2 mmcblks that are +- 8 MB
[Samsung Epic 4G Touch] datajosh:
7 is cache it looks like

C:\Users\Josh>adb shell cat /proc/mounts

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,relatime,mode=111 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0

/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0

nil /sys/kernel/debug debugfs rw,relatime 0 0

/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0

/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0

/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fm

ask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro

,discard 0 0

/dev/block/vold/253:1 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,

gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors

=remount-ro 0 0

/dev/block/vold/253:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=101

5,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remoun

t-ro 0 0

tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[Samsung Epic 4G Touch] shabbypenguin:
ok so 9 is system, we need that. gunna guess that 8 is prolly one.. but usually they do it in order, so the cache being 7 is certainly weird. but no matter.

chains it certainly an very welcome surprise to have you here helping out ;)
[Samsung Epic 4G Touch] Chainfire:
Just looked it up, on original SGS2 it is #5 that is kernel. Not sure which one the backup kernel partition is (if used at all)
[Samsung Epic 4G Touch] Calkulin:
It looks like it's 4, 5 or 6, so I'm guessing it's still 5 like the original

major minor #blocks name

179 0 15387648 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 307200 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 2097152 mmcblk0p10
179 11 12066816 mmcblk0p11
179 12 319488 mmcblk0p12
253 0 15663104 cyasblkdevblk0
253 1 15662080 cyasblkdevblk0p1
[Samsung Epic 4G Touch] shabbypenguin:
im just gunna throw out there that 5 is prolly boot kernel and 6 is recovery kernel
[Samsung Epic 4G Touch] datajosh:
And I guess we need superuser access to pull it?

C:\Users\Josh>adb shell dd if=/dev/block/mmcblk0p5 of=/sdcard/mmcblk0p5.img

/dev/block/mmcblk0p5: cannot open for read: Permission denied

C:\Users\Josh>adb shell dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.img

/dev/block/mmcblk0p6: cannot open for read: Permission denied

Edit: Calk, you picking up one of these too?
[Samsung Epic 4G Touch] Calkulin:
Well it seems you are right because according to the pit file that was posted in another thread, 5 is the kernel and 6 is the recovery.

---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------

I already have one :cool:
[Samsung Epic 4G Touch] antihum4n:
Oh **** we got calk now we need toast, netarchy, and shinzul
[Samsung Epic 4G Touch] shabbypenguin:
yea you need root to dd

so we need someone who has root or is brave enough for a moment, to flash the rooted sgs2 kernel, pull 5/6/9 mmcblk's and upload em, i can then make a prerooted system tar, get someone else root and pull stock kernel and everyone can have root and working radios
[Samsung Epic 4G Touch] Issey_phresh:
Seeing you 4 work together on this us just beautiful! BEAUTIFUL! Good things to come for the epic touch!
[Samsung Epic 4G Touch] datajosh:
Awesome! My wife and I had your EVO ROMs on our phones longer than anyone else's... glad to see that we weren't the only ones to give Samsung a chance :D

If I wasn't about to leave for work I'd go ahead and do this, hope someone else can step in and get it going :)
[Samsung Epic 4G Touch] iSaint:
Loving the Teamwork guys !
[Samsung Epic 4G Touch] darren.wlsn1:
lol, kernel roots phone so.....
[Samsung Epic 4G Touch] xlGmanlx:
Some people have reported issues with losing signal and not even been rooted
[Samsung Epic 4G Touch] darren.wlsn1:
i get that but why are they posting in a kernel thread that roots your phone? sorry i guess its me
[Samsung Epic 4G Touch] 12MaNy:
I agree...

....pleeeeeease Z?!

Yeah, so far this forum is a disasterpiece. I thought for sure that there would be a bunch of seasoned vets all over this device from day one. I mean....it's a SGSII for f*cks sake! Oh well....the "devs" that are in here will get better over time.....and kudos to them for what they've accomplished so far. :)

+1

The more info about your setup your post, the better chances you have of getting your issue resolved.

---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------

Ummmmm.....to try to prove that it's not the kernel?
[Samsung Epic 4G Touch] odub303:
Dude, if it was that easy he would have done it already. People are working on getting a fully stock kernel, be patient!
[Samsung Epic 4G Touch] Fus3D:
Exactly
[Samsung Epic 4G Touch] 12MaNy:
You obviously didn't read the post I quoted.....dert da der. Lol

I'm rooting Z on in a way. Go bite down on a blasting cap. :)
[Samsung Epic 4G Touch] odub303:
Whatever you were trying to do did not come across in your post.
[Samsung Epic 4G Touch] Vegasden:
If the "vets" are like a good many folks that ordered through 3rd party sellers, they might not have gotten their phones yet. Let's Talk, as far as I've read, hasn't even shipped yet. The "devs" that have been active have done a creditable job albeit more behind the scenes testing would have probably been warranted.

....
[Samsung Epic 4G Touch] dutchman71:
Ok, I just lost service 1 1/2 day after rooting... Bug finally hit me.. Bummer
[Samsung Epic 4G Touch] XxElitexX:
I have 2 E4GT's that were not rooted and had the no signal/voice/data issue. Upon updating the PRL the issue was resolved. After rooting one of them I am happy to say the issue has not returned. Great work!:D:D:cool:
[Samsung Epic 4G Touch] plmiller0905:
Maybe the issue is that sprint is working on their network in various cities. That'd why some people is having the no data issue and some are.

I dont know for sure, I'm just speculating...
[Samsung Epic 4G Touch] XxElitexX:
Hmm, I'm surprised this wasn't mentioned before. Good observation...
[Samsung Epic 4G Touch] comedy:
Couple updates just from MY experience, hope it stays this pleasant.

3g/4g works

WiFi works

no dropped calls or unrecieved texts (although not really sure how we'd all know unless your gf starts *****ing at you randomly for not answering her texts for 2 days :P)

the only problem ive had, like i said before was my quadrant score has gone down around 400-600 points (to 3k) after root ..

did rooting reset the cpu speed by any chance? or lower it below 1200? thats the only thing i can think of.
[Samsung Epic 4G Touch] deano0714:
I just read acs extracted the kernel so we will have a stock kernel with root!
[Samsung Epic 4G Touch] xlGmanlx:
hey, for you and all saying non-rooted and rooted, can you also say what your PRL exactly is? That also might help folks out
[Samsung Epic 4G Touch] comedy:
b e a utifulll! :d
[Samsung Epic 4G Touch] plmiller0905:
I'm starting to believe that's what it is. I mean, I know I complained earlier but when I went to the sprint store, the Rep informed that he has been having the same issues and that sprint is doing work on the network. Which I seem to confirm, cause once I left the store I had 4G...and I remember awhile ago there was no 4G service our here. Although the signal was weak in some areas, it was there.

So for now I'm gonna put my money on that instead of the kernel or a Samsung bug.
[Samsung Epic 4G Touch] superhtchd2:
Had my first issue with signal loss today , did the root early yeaterday and didnt notice any issues..well did the overclock kernel last night and just had twice within the last 3-4hrs loss of signal and had to restart the phone to get it working again .. Any confirmation if this is from the kernel or unrooted phones experiemcing this also?
[Samsung Epic 4G Touch] plmiller0905:
where at...link?
[Samsung Epic 4G Touch] deano0714:
I read on there kernel thread but no link yet :( idk if they have relased a fully stock kernel..
[Samsung Epic 4G Touch] xlGmanlx:
i was thinking the same thing!
[Samsung Epic 4G Touch] comedy:
Anyone have a fix for the Quadrant score drop, or a work around solution?

(3400-3600 stock, now at 3000).
[Samsung Epic 4G Touch] KLLSWITCH:
overclock then put governor to performance
[Samsung Epic 4G Touch] Vegasden:
I can tell you here in Vegas they are working on towers. Using Tasker I did a "cell nearby" scan a couple days ago. Normally I have 3 towers show, but I only got 2. Today, the tower that is closest to my home popped up (missing on first scan) yet the original 2 did not.

Anyone look at other phone forums to see if data loss is being experienced?

....
[Samsung Epic 4G Touch] 12MaNy:
True...I see your point. I just got all antsy in my pantsy. Trust me, I'm not trying to take away from anything these guys have done. I've been patting these guys on the back and I've been speed-bagging the Thanks button.

Not sure, but my NS4G (backup) hasn't experienced any data loss/fluctuation. Neither have my kid's Evo and Optimus S.

Nice! Good job ACS! :D

---------- Post added at 12:37 PM ---------- Previous post was at 12:36 PM ----------

Eh....you took it that way. Chill out bro...:)
[Samsung Epic 4G Touch] Fus3D:
Booya, 4400!

No data loss issues or anything.. Just called myself, all good at 1600!
[Samsung Epic 4G Touch] comedy:
Im a little confused, after rooting & getting setCPU it cant go past 1200, its still set on performance, and im still getting the same scores..

im not trying to OC really, im just trying to get my original Quadrant scores back, other people have experienced this, im not taking crazy pills right? :eek:
[Samsung Epic 4G Touch] xlGmanlx:
did you auto detect the device? The kernel sets the cpu speeds so if its the latest you should be able to change it. Also make sure that you gave setcpu root access
[Samsung Epic 4G Touch] Fus3D:
Smashing all benchmarks!

Sent from my fast ass GS2
[Samsung Epic 4G Touch] zedomax:
Download this kernel and flash it, you will get the performance back without overclocking.
[Samsung Epic 4G Touch] comedy:
Im sorry, which kernel?

Outstanding work nonetheless by the way Zedo ;)
[Samsung Epic 4G Touch] KLLSWITCH:
after you flash the kernel you have to open setCPU and hit the menu button then hit auto detect then it'll ask you to confirm click ok then you should be able to overclock
[Samsung Epic 4G Touch] Fus3D:
I need to go back stock, transitions seemed smoother the way they were stock. Prolly gonna just use my free replacement through best buy protection program and run this beast over with my car, no evidence of tampering and no way to even check a board cracked in a million pieces, lol
[Samsung Epic 4G Touch] JohnCorleone:
Zedomax has 2 kernels out. Flash the overclockable one. It has "4000+ quadrant " in the title. Also, if you already have SETCPU installed, you may just need to use the maximum slider and move it around and you will see it go higher if you overclocked
[Samsung Epic 4G Touch] comedy:
Zedo had it right above ^^ .. im not trying to overclock, im just trying to get my original quadrant scores back, cause they've gone down... even with setCPU on performance @ 1200 i still get lower scores than before.

i know this is all a fresh & early build, like a newborn baby, but just lookin for any advice on how to fix it, and/or waiting to go back to stock & wait till the bugs get sorted.

again, just to restate..NOT trying to overclock, just trying to get my scores back.

flashing the other zedomax kernel seems very contradicting to what im trying to accomplish ;[.
[Samsung Epic 4G Touch] tool2269:
please make video of this lol
[Samsung Epic 4G Touch] 12MaNy:
+1

10char
[Samsung Epic 4G Touch] Fus3D:
Lol I sure will, lol.. Will b fun, lol

Actually thinking about doing a torture session. Any ideas, I want to punish the phone before starting the crushing part! So I'm thinking, throwing it into a spinning fan. Or dropping it into the garbage disposal lol. Hmmm vat to do, vat to do.. So many options
[Samsung Epic 4G Touch] 12MaNy:
Or, you can throw it into a wood chipper (that would be awesome to return a box of phone dust and look the rep dead in the eye with a smile on your face and say "Ooops!")...or, you can drop a bowling ball on it from 3 stories up and yell "Steeeeerike!"....or, you can stick it in the microwave for 30 minutes, then cool it off in ranch dressing...or, you can squirt lighter fluid on it and set it ablaze Jimmy Hendricks style.

...but the all time best one would be to walk into a Sprint store and tell the rep that you may need a replacement in about 3...2...1, then yell out "GODDAMN HELLFIRE!!!" and He-Man spike that ***** on the counter as hard as you can, then apologize to the people in the store and try to explain that you have turrets and ask if they have insurance that covers that.
[Samsung Epic 4G Touch] SSaxman:
Just be aware that there are different PRL's for some areas. Some have 60xxx and some 20xxx.
[Samsung Epic 4G Touch] woodyth:
60681 here
[Samsung Epic 4G Touch] zarthan:
I asked the Manager of my local Sprint Service Centre about rooting the phone. His reply was to show me his rooted phone. He said the official stance is that Sprint is a part of the Android Development something or other and there is no issue with rooting your phone. If you have rooted your phone and have an issue that they will try and return it to a stock image. If you brick it they will replace it. How often they will replace a bricked phone is unknown. Get friendly with someone at a Sprint Service Center.

Edit: Forgot to mention. The Manager pointed me to the XDA forums as well.
[Samsung Epic 4G Touch] XxElitexX:
my PRL is 60681
[Samsung Epic 4G Touch] muzicman82:
So, I've been rooted since instructions were posted, and I've been getting the No Service/Signal problem every 6 hours or so. A reboot fixes it.

The first time it happened, I thought it was simply an activation thing. I ordered this phone with the upgrade credit from another line from a 3rd party reseller. I activated it manually onto my line. Everything was fine and then 24 hours later, my phone because the other number. I think they must have had an automatic activation or something. I chatted with Sprint and they sorted that out.

So, now, it turns out it really is the bug.

Is a new rooted kernel in the works?

What happened to rooting methods involving using ADB Shell?
[Samsung Epic 4G Touch] plmiller0905:
I tried that earlier today and was told I had to return it to stock. I wish they would've exchanged it but they didn't. I'm gonna call them in a bit here and try to get one
[Samsung Epic 4G Touch] XxElitexX:
I've returned root phones running custom ROM's and have never had any issues.
[Samsung Epic 4G Touch] tetracw:
having an issue with a yellow triangle with an exclamation point appearing at Samsung Glaxay S II splash screen on boot. Also an issue where MSL reader cant get root access. says "error: /dev/smd0 does not exist, phone is not compatible" Everything else seems to be working. Wireless tether is working fine.

Any ideas? Anyway to undo?
[Samsung Epic 4G Touch] stangdriverdoug:
The Yellow triangle is normal and MSL reader only works on HTC devices. You need to get the MSL code by using terminal emuator.
[Samsung Epic 4G Touch] Fus3D:
Lol I would love that but thats too risky, lol. Lighting it on.fire sounds good, and wood chipper was hilarious, phone dust heh
[Samsung Epic 4G Touch] JoshBeach:
I did not root until today, and ive had phone since 10AM Launch day. I did NOT have ANY issues at ALL stock. I flashed Zedomax's V2 overclock with CWM today, because i saw a bunch were ok with it, and I havent been able to get 3g or 4g data working at all. the phone is stuck in airplane mode. BUT i can get WiFi... Weird. Phone in Airplane mode, wont come out, but wifi works... also none of my Apps work, except the native apps. everything else FC's right away. We really need to find a way to Odin to unrooted stock, or flash through CWM ASAP... Lets make that a Priority!!!
[Samsung Epic 4G Touch] fbyers59:
Unrooted, no data problems. PRL 60681
[Samsung Epic 4G Touch] XxElitexX:
LMAO!!:D:D:D:cool:
[Samsung Epic 4G Touch] xenide:
Have exact same PRL and I'm rooted. Data and voice problems occurring when I open the dialer and try to make a call 30 minutes after making a previous call.
[Samsung Epic 4G Touch] frieked:
Same here, had the phone since Saturday and so far no issues at all.