Related
Okay, there is some misinformation going on.
If you are running a stock EVO, 3G works fine (I just did the 25MB speed test at testmy.net and averaged 1.1Mbps - when ROOTED, I can't get the 6MB test to finish).
When running a rooted EVO in Denver, for some reason, 3G cuts out constantly and won't last more than 2 minutes... generally about 30 seconds and then it dies for a few minutes or until you make a phone call, reboot, put it in airplane mode, etc.
I have tried literally EVERY ROM including the "stock rooted" ROM and they ALL exhibit this behavior.
The only thing I can think of is that something is amiss when flashing the new radio without using the official HTC update package but I'm not feeling like re-rooting my phone all over again with the old radio just to find out.
How many people are experiencing this?
I rooted my EVO and began having issues... Probably about the 13th as stated in the thread... Got really annoyed and flashed the stock RUU (had to take the rom.zip from the Temp folder and rename it to PC36IMG.zip in order to flash though because RUU would not find the phone)... Problem instantly was resolved. Ran the OTA update to get the new radio, thinking it was a radio problem, nope. Still works perfectly fine.
I decided I wanted to try EVOlution V8 today so I re-rooted. Right off the bat, 3G issues. I rooted manually, then NAND, then recovery, then flashed the new radio, REBOOTED, went back into recovery and flashed the ROM...
Now I just ran the RUU and flashed back to stock and everything is working fine. So there is something about the procedure to root that is causing the problem and I don't know if its Denver-specific or what...
I can tell you I didn't have any problems until I unlocked NAND and flashed the permanent recovery. Toast's original root gave me no issues... but that may just be coincidence.
If I decide to stop being lazy, I may re-root and skip updating the radio and see what that does... But for now, I have to conclude it is a rooting issue, NOT a network issue.
I think we need a new Poll for anyone that needs to change their answer after upgrading to JK4...Perhaps give JK4 a few days to make sure it's running smoothly before voting...
(Thanks Electroz for the original Poll!)
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty...
I don't think there are any issues with Kies or Odin for flashing. I've flashed many times, sometimes 4 times in one day and I've never had any issues. There does seem to be the usual SD issues but I also think there is a USB communications issue. There have been many reports of data corruption while writing to internal/external SD with large files. I personally had an issue pulling large files off of internal/external SD. I think if this problem occurs while flashing new firmware it could cause some corruption that could be noticeable right away or after a bit of use. The partitioning on this device seems to be more sensitive than others and a hiccup while flashing could cause some major issues.
trinitonesounds said:
I got to experience 5 minutes of froyo before multiple force closes and then dead. It went into a reboot loop never getting past the white i9000m logo.
Updated with Kies (latest version--no registry mod)
I was stock JH2.
No lagfix ever installed
I've never flashed any rom.
Sorry guys, Kies is not safer...
Now I have to convince Bell to honor the warranty even though I'm on Rogers...
Click to expand...
Click to collapse
They don't care.
I went today and they just took it and didn't ask anything that sounds like they cared about if I am not with Bells.
I gave them my bro's phone number and info since he is with Bell, just to avoid any problems.
Just don't say something like the phone is "unlocked" lol...the phone is dead so they won't find out anyways if you don't tell them. They won't ask either.
Just tell them that you upgraded through kies and it got the problem.
it's a hardware defect, if it dies it dies
after all the evidence we've seen (all the reports by our members)
if it's good it will work regardless of what firmware you use, and regardless of the way you flash the firmware
the lag fixes and froyo just accelerates the problem and makes it more evident sooner than later
which is good in a way, it's better to find out before your warranty runs out
ok im pretty sure mine is a full brick. maybe you can tell me.
less than 24 hours after updating to 2.2 i started getting all of these errors in various programs, so i rebooted the phone, but after it plays the little intro thingy the screen just goes black and thats it. cant do anything else. i tried a factory reset and still the same thing. so is that it?
also. i bought this phone at best buy, but network unlocked it to use on rogers. should i be contacting samsung directly about a replacement/fix? anyone here done that? im REALLY scared that are gonna give me a phone that i am unable to network unlock.
thanks for any info.
some one welcome me to the club of defund Bell Internal SD
http://forum.xda-developers.com/showthread.php?t=867157
@evil-doer
I am in the exact same boat as you! I bought from Best Buy, then unlocked to use on Rogers. Last night, I updated to official Froyo through Kies, and then it just died on me today (many app force closes and then just drop dead). When I get into recovery mode, it says can't mount the SD card.
I think I will just go to a Bell Store tomorrow and see what happens. I will let you know how it goes. Please let me know how yours go too. Thanks.
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
i did not have Force Close, the phone just got really really hot during batch restore of TitaniumBackup
jdrom said:
Mines a goner too
Same issue, have a forced app closure, shut the phone off and it wouldn't start up anymore. Just flashes the Galaxy S GT-I9000M white logo non-stop now.
I can put it into download mode and load up 2.1 (stock) and get to the coloured Galaxy S logo, but then it just goes to a black screen. In recovery mode, it shows stuff about not being able to mount the SD on E:\. I'd assume that's the internal flash?
Luckily I haven't had it for >30 days (on Virgin Mobile) so I'm hoping I can just exchange it and be on my way. I have to call them though apparently since I bought it online.
Click to expand...
Click to collapse
how did you load up 2.1? i can put my phone in download mode but nothing happens after that. and how do you get in to recovery mode?
Well I can load up 2.1 with Odin and with the auto reboot option checked, it'll go straight to recovery mode after flashing (for whatever reason). Otherwise I can't get to recovery mode.
Success so far... 12 hours after upgrade.
I sucessfully upgraded to Froyo yesterday.
I had problems with Kies at first and had to do a factory reset before the upgrade. The FileSearcherforKiesFix.exe altough it detected two bad files wasn't enough to make Kies happy.
This phone was bought in october and had the voodoo lagfix installed from the begining. I disabled the lagfix before the froyo upgrade.
My previous samsung phone; the GT-8000 (Omnia II) did have an internal SD card failure after a few months of operation... Also a Bell phone. I'm really concerned by that trend with Samsung and Bell...
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Well... you're going to have upgrade eventually so best to do it now while you are under warranty in case something happens...
nemethb said:
I recommend NOT to upgrade. With JH2 I had NO problems. I upgraded to JK4 and about 24 hours later (this morning) I started getting force closes. XDA App. wouldn't open and just scrolling through memory management gave me haptic feedback (even though I had it disabled) and random closes. The phone became unusable fast. I tried a reboot and the phone booted to a black screen where only the buttons lit up. I went into recovery mode and I saw some dbdata error. I figured my phone was a goner. I ended up formatting the internal memory, clearing cache and then doing a factory reset. The phone is up and running now...but for how long.
Click to expand...
Click to collapse
How's that the case?
Stock JG9 w/ OCLF -> Stock JH2 (kies,voodoo lagfix) -> JK3 (Odin, Speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix) -> JK4 (hacked kies, speedmod kernel w/ tweaks flashed through odin to get 2e back, no lagfix)
No SD failure so far, touch wood. Original phone purchased day after launch.
Mine died today, started getting FC and then the whole thing froze. I tried restarting it but after the samsung splash screen all I had were glowing buttons.
It ran fine for about a day on JK4 before that on JH2 it never gave any problems.
BTW it was stock updated through Kies.
The guy at the Bell store told me they never get these phones returned, this was a first for him. Either it was his first day on the job or it's typical Bell BS.
Just had my second phone die. The first one died after 28 days with no upgrade. This one after 8 days, 2 days after upgrading to Froyo...
Same thing happened to me this morning.. Froyo was working fine for just over a day and then this morning I turn on my phone, get a bunch of FCs.. I reboot.. get another bunch of FCs.. reboot.. and now it won't go through the "S" splash screen. When the screen disappears I press the buttons and it just glows..
I don't know if it's bricked or what.. when I run recovery I get this error.
E: can't mount /dev/block/mmcblkOp1 (I/O Error)
E: Copy_dbdata_media:can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
Is this what everyone else is getting? And what are my alternatives?
If my phone is pooched then I'll be pretty pissed since this is my 3rd SGS, I gave the SGS up when it had issues in low reception and the 850 band lock fixed it. If this totally pooches my phone I'm never buying another Samsung mobile product again.
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
blackied said:
Hi, about 5 days ago my wifi stopped working. I'd turned it off a few days earlier since I didn't need it. When I try to turn it back on now though, it takes a few seconds and then says error. I'm not sure what's wrong with it.
Since then I've reflashed my phone rom (leedroid), factoryreset it, and updated the radio. nothing so far has fixed it. Mobile data still works so I wouldn't think it was hardware, but a software error shouldn't have survived the wipe and the radio update.
Does anyone have any suggestions?
Click to expand...
Click to collapse
I had similar issue when flashing another kernel on my stock ROM. Maybe your kernel isn't compatible with the radio or the kernel modules haven't been applied correctly. Hardware error should be presumed after flashing original RUU.
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
blackied said:
The thing is that I hadn't played with my phone since last year. the wifi just randomly stopped working. It was still on 1.22ghz kernel 1.0.2. It got reset to stock kernel when I factory wiped it.
I've gotta go travelling again for work tomorrow so I'll try flashing the original ruu back next weekend. Would it just be a case of restoring the original nandroid backup I did before I first h-booted/rommed it?
Click to expand...
Click to collapse
As far as I know, factory wipe deletes just the user data. I might be wrong though, because this is my first android, so I'm still learning the basics on rooting, kernels, etc. But from your first post it seemed that you updated your radio in that period, so this might be the clue to what happened. I don't know if the nandroid backup would restore everything to stock, but I'm pretty sure that the original RUU would. Still, you should follow a procedure that would allow you to keep your root (I think if you have radio S-OFF, you'd be able to flash 1.32 RUU and just root it). Anyway, you can't return the phone for warranty services with a custom ROM, so you still need to flash a stock RUU.
Sorry, I should clarify: I did the radio update yesterday to see if it could fix it. It wasn't the cause.
One more question, im not to sure of this program ODIN, but i remember i did a factory reset to get my GPS working a few weeks ago. I followed this post
""Fixing the GPS no fix issue on the Samsung Epic 4g requires you to do a manufacturer's reset by obtaining the MSL code from Sprint. Once you get the MSL Code, remove the SD Card and Enter ##786# on the dialer keypad. You will see two options: View and Reset. Tap on the Reset option and you will get a prompt to enter the MSL code. At this point you will be asked if you want to do a manufacter's reset, enter yes. The phone will shut down and reset itself after a few seconds. Once the process is complete, the phone will go through a hands free activation. After the activation process, updates may be downloaded and installed. Now that all updates have been performed, you may check to see if your GPS is working by going to Google Maps. You should be able to lock in GPS signal in under 10 seconds. Thats it. Your GPS woes are over."
After i did that and got a GPS lock, i went to CWM and did a ADVANCED data restore, and i back on DK28 and had GPS lock when i went into maps. COuldnt i jsut do the same factory reset, then open up CWM, flash the DEOXED eb13, and then do a advanced data restore??
Major question would be if i did ADVANCE, would it bring me back to DK28, or would i just do a DATA restore.
I really was hoping there would be a easier way to go from Dk28 to EB13, but this way seems alittle easier then ODIN.
Flashing the DK28 rom will NOT update the modem to EB13. Use Odin or samsung updater program. Both are very easy, just follow instructions.
Well to answer my own question, it says it does a MASTER RESET, but it DOES NOT!!! I ended up resetting my phone without my data but still am on DK28 with the ROM i flashed. And to make matters worse, somehow i ended up wiping all the data off my SD Card in the process, not sure how, Good thing i copied all my info to my laptop earlier today. I am now putting everythign back aswell as the DEOXED EB13 rom which im going to try and FLAsh the zip via CWM. worse case scenario i just advance rstore back to my CW backup from today and its like i didnt do any of this. ugg
If you are trying to get back to Stock (not rooted) just use the Samsung tool for EB13.
As far as going back to DI18 2.1, you will be better off with EB13 flashed, not the update.
im trying to go back to DK18 and stay rooted, to update to EB13.
urirx98 said:
im trying to go back to DK18 and stay rooted, to update to EB13.
Click to expand...
Click to collapse
Why not just use the samsung update tool, then use CWM 2.5.5
http://forum.xda-developers.com/showthread.php?t=770388
to root it. You will get a clean install (recommended) and root.
ok, so i actually was able to FLASH the DEOXED version of FROYO EB13 ontop of my DK28 , dont ask me how, it told me it didnt work, but it did. Now i tried to CWM my data and its saying its a non match. THis is not making me happy. I heard people had probs with this, any way to fix it??
Edit, i actually accidently swapped SD cards when i was copying and pasting and when i replace it with the correct card, i had no problems doing a FULL DATA restore.
I KNOW HAVE SUPERNOVA 2.2.2 EB13 Kernal version 2.6.32.9 running Firmware GENOCIDE 0.3a EB13 OC/UV kernal
Its KICKASS!!
I would odin to stock eb13 and if you really want everything to work try ACS FROZEN rom. Ive never been so happy with my device it ALL works
Hi.
I have an issue where my phone keeps freezing and restarting.
sometimes it stops a the download recovery screen so i have to remove tha battery, it does every now and again say something about mcc read error in the top left on boot.
I have wiped, taken out sim and memory and reset to factory but that was good for 10 mins then it started again. Its still under contract and warranty but im worried they wont fix as i rooted it about 1 year ago but lots root 6 months ago with the updates.
What can i do before i send it in so they cant see it was rooted and voided warranty.
Thanks
Stu
Welcome to the club
http://forum.xda-developers.com/showthread.php?t=3439111
http://forum.xda-developers.com/note-4/help/note-4-910f-ddi-mmcread-failed-t3465277
http://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
plus many other posts.
Flash a STOCK Rom, send it for repair and hope for the best?
I'm on the same boat as you, my phone is still under warranty but rooted. I installed Wake Lock - PowerManager to make the phone usable.
lol.
It does have stock rom, i rooted when it was the version before marshmalow, then when the 6 update was released by my phone co it updated and i lost rom. I did read though how it says custom in settings
Have the same restarting problem. Tried reinstalling stock rom. And it didn't accept it
Sent from my iPad using Tapatalk