Related
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.
Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.
Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant
I can't seem to find Damagedtrev 2.01
So I can't test it.
Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.
Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?
Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221
Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.
Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?
I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd
Tomorrow is my 46th birthday, and I have tried to stay on top of technological advancements as best possible given my busy schedule. What I have noticed is that my ability to digest the latest techno trends and techniques does have a limit, especially when it interferes with the approaching martini hour at afternoon's end!
I don't know if this is a question or a mid-life existential moment. I bought the Samsung Epic 4G last fall because it was supposed to be cutting edge in terms of hardware for Android, and I as many of you have expressed, I made the decision to buy the Epic because of the promised firmware update that was imminent.
Fast forward half a year, and I now have the 2.2.1 EB13 firmware, which is rooted. I received the SMS yesterday (Wednesday) afternoon from Sprint about Sprint ID coming, but no update. Since I am rooted on EB13 I have no idea whether or not I will ever get the OTA and the last time I tried ODIN I had to take a tranquilizer, so I have no desire to go back to 2.1 to get the OTA.
Will the EC05 OTA be appearing given rooting on EB13? EB13 is giving me problems. I loved moving many (most) apps over to SD (I have a 32 gig card). But WiFi is not good, and I lose the ability to play movies, audio files, visual voicemail, or even hear my phone ringer (all seem connected in terms of the error -- I get an "unable to play message" or "unable to open file" error). I have to turn the phone off completely, then back on, wait for the media scan, etc. for it to go back to normal, then the errors will come back. I was hoping that EC05 would fix this. Maybe not. In perusing and searching I see nobody else has reported these problems which did not exist on DI18 (although I do see reports of WiFi connectivity problems that appear similar).
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
UPDATE: Life is grand at 46 (almost!). I posted later the following URL:
hxxp://forum.androidcentral.com/epic-4g-rooting-roms-hacks/71389-odin-ec05-froyo-ec05-prerooted-cwm-v2-5-1-0-rfs-odexed.html#post761525
When I got home I did as instructed using ODIN, and now I have EC05, with root, no data erasure, all is well! I still see so much consternation going on in the other threads. If you go to this URL and follow the directions, it works without any issues. I noticed immediately my WiFi issues are issues of the past. You can either wait for Sprint/Google to OTA you, under certain limited conditions, or do this, and be whole. Your choice. JJP
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Thank you, what a nice response. Hopefully an update.zip will appear for EB13. Stranger things have happened.
drplaud said:
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
Click to expand...
Click to collapse
Unfortunately, all the AMPS and Digital TDMA networks have long since been shut down, so it would do you no good
But I do have a bag phone haha
Sent from my SPH-D700 using XDA Premium App
I wish I was 18 again, but for other reasons.
Yeah it is hard to keep up with tech these days,it changes by the hour now. And Ill have to say that Android is fragmented,this makes it harder; Look at what 2 updates to 2.2.1 and a 2.2.1 leak has done to this Epic forum,it has become a mess,I just hope now that we have CM7 and probably the last update for atleast 6 months,we should start to see some serious progress.
Sent from my SPH-D700 using XDA Premium App
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
I do not think I will receive the OTA as I used one click to root after installing EB13. Perhaps this is the time to go Bonsai as I understand it now has EC 05 built in. I apologize, but is there a primer on how specifically to go to Bonsai? I have never flashed before (as I thought I might be arrested). Thanks.
Sent from my Samsung Epic™ 4G
You mentioned you're rooted. Do you know if you have CWM3 installed?
Its all a little trial and error but once everything is properly installed flashing roms is a cinch. I'm a big fan of the ACS roms. Bonsai worked well on my phone but there were a handful of idiosyncracies present that I could not put up with. Of course YMMV but don't hesitate to try different roms until you find one that your phone works well with.
stir fry a lot said:
You mentioned you're rooted. Do you know if you have CWM3 installed?
Click to expand...
Click to collapse
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
drplaud said:
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
Click to expand...
Click to collapse
Cool. If you want to give EC05 a shot, go to this thread and download the modem.
http://forum.xda-developers.com/show....php?t=1003447
Insert the modem into the Phone section of odin and hit start
Put aside some time before proceeding. If you have the correct CWM installed it won't take more than ten minutes but play it safe.
Download a rom of your choice, plug your phone into your computer and place it in the root of your SD card. You can download multiple roms if you want to see which works best for you. You will lose all your data the first time installing any new rom as it is not really recommended that you transfer settings of apps between different roms. Once you find a rom your're happy with you can simply update it it with the newest version without having to wipe your data however. Its really not as bad as it sounds and the ACS rom comes with an excellent app recovery program called MyBackup Pro Root that you can backup your apps and data with. You can use it to transfer apps between different roms and even some data but data from different roms can sometimes give you problems and is not really recommended. I have transferred data with some apps without any problems however. Its really just data that is tied to the system itself that will probably give you problems.
Unplug your phone from your computer and long press the Power Button, select Reboot, and then quickly hold down the Power, Volume Down and Camera Buttons.
Now press and hold down the Power, Camera, and volume down buttons. It should boot to the samsung logo and then to a black screen with orange text on it.
Use the volume keys to navigate and the power button to make selections. Choose Wipe Data/Factory Reset and wipe it 3x, then do the same for the Cache Partition and Dalvik Cache which can be found in the advanced options.
Select Go Back and navigate to Install Zip from SD card. Choose the rom you downloaded to it and you're good to go.
If after you do the three finger boot and you're not brought to a black screen with orange text you will need to install the correct CWM. If its black with green you have an old version and if you get a different screen than that this means that you do not have CWM at all. If this is so, just navigate to reboot and press the Home key to select it.
Something to think about
Thank you for the very helpful responses. I will ponder what the best option is, but it may indeed be time to explore custom ROMS, and your responses have given me the courage to do so. Many thanks! Joe
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
I would Odin to EC05 first and see if it fixes anything for you. If not, reboot your phone into CWM and if you have the correct (orange and black) version, just reboot load the ACS rom onto to your phone and give it a try. If you're not happy with it or even if you are make a backup with Mybackup Root and explore other roms until you find one that works for you.
If you make a backup I would advise making separate backups of your apks, data for your apks, and photos as it makes it much faster to get back to where you were originally. Another tip for my backup is after making one go to View and double check that it actually made one as sometimes it will not.
I would have thrown this phone away by now if it weren't for the ACS rom btw. Its much smoother, has better battery life, doesn't skip keys even without the patch that they will be implementing soon and doesn't have all the god awful bloatware.
musclehead84 said:
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
Click to expand...
Click to collapse
Where do I obtain one click root with cwm3? Thanks.
musclehead84 said:
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Click to expand...
Click to collapse
stir fry a lot said:
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
Click to expand...
Click to collapse
I agree with all of these except that odin never gave me trouble even the first time i used it..
Odin is cake just read the simple directions and everything should be fine, people dont use there heads when they get that android dude and the computer on there epic, the most ive been through is acore of force closes but its so easy to fix,
people just dont read the instructions all the way through,
Yesterday i was scared to update the prl manually but i read step by step instructions had to play around and find what i needed to do which wasnt on the instructions, and it was cake, almost just as easy as clicking the system updates/update prl button in the settings
but 98% of the time the instructions are flawless and work as long as you read carefully and do step by step.
drplaud said:
Where do I obtain one click root with cwm3? Thanks.
Click to expand...
Click to collapse
Development section stickied
Called One Click Clockwork 3.0.0.6
Oh yes happy birthday as well, have a great one!!
IMO, if you are on EB13, and want to update to EC05, the EASIEST way to do it, if you can wait a bit, is to use the stock SWUpdate for EB13, which will convert your phone back to a clean fresh stock install of EB13, then once/when it is released, install the EB13 to EC05 update via the over the air process, then reroot and move forward.
that all depends on samsung/sprint releasing a EB13 to EC05 OTA update, and your ability to wait for it though
So this morning I got a call from a friend who told me that his TF is running like crap after doing OTA upgrade to ICS.
We met up at school and I got to take a look at it. Yes, it was indeed running like crap and it even randomly rebooted while we were eating breakfast. He told me the random reboots were happening every 3-5 hours(that he could notice).
Here's what I did to fix it.
Removed his MicroSD card(not sure if necessary)
Shut down TF.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen. Left icon is Wipe Data. Right icon is Cold boot. Right icon is selected by default.
Press [volume down] to highlight the LEFT ICON, which is Wipe Data.
Press [volume up] to confirm your selection
Go through the process.
Let your TF reboot.
Shut down TF again.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen.
You need to do cold boot. It's already selected by default so just wait like 10 seconds and it will happen automatically. Press [volume up] if you don't want to wait.
Go through the process. Your TF will reboot afterwards.
Done.
It has been over 24 hours and his TF has been running smooth without any glitches or any random reboot. I told him to let me know immediately if a random reboot happens again.
This is simple to do. Worth trying unless you can't read English.
Edit: I didn't include this at first because I thought it would be common sense for everyone but it apparently isn't....
DO NOT JUST RESTORE ALL YOUR PREVIOUS APPS AND WIDGETS YOU HAD FROM HONEYCOMB. THAT DEFEATS THE ENTIRE PURPOSE OF DOING A RESET AND PREVENTING APP INCOMPATIBILITY.
thnx man for sharing . I actually tried every thing to solve this issue but no luck , I'll try your as sson as i go home .
This did indeed work for me as well. I tried this a couple days ago and I have yet to have any freezes or random reboots. I think that not restoring any backed up data, apps or settings is key to fixing the problem. I'm now very happy with ICS- burn in hell Honeycomb.
Shameful bump
When you switch from a version like HC. This is what you exactly should do!
I did this and never experienced random reboots.
My Transformer is running since three days and everything works fine!
Edit:
Another quick hint:
If you want to work with Google Docs, you have to disable Forced Hardware Rendering!
I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk
billouetaudrey said:
I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
.....lol, why post in this thread that you are not going to follow the advice of the Op?.......
Sorry to say but this is not working, already done this since the minute it was out and still have so now and then a hang boot
(random reboots that hangs on the boot)
Giving it a try
I am experiencing random reboots after ICS
Wiped transformer, cold booted, and installed the following.
Adobe Reader
Dog Catcher
updated G+ and GMail but have not run it.
Charging now, I will let you know.
Previously I had wiped it and reinstalled all, disabled syncing, disabled location info, adjusted wi-fi settings, and added CPU throttle control obviously none worked.
It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.
JesterOC said:
It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.
Click to expand...
Click to collapse
why are you installing dogcatcher? And this does work.. do it again. Don't install your apps.enusre it dos not lock up before you install anything.... If it locks up before you install any apps then call Asus. If not start installing one app at a time. Wait after each install. Ensure that its not doing it, once you are sure install Another ....rinse/repeat....
I installed dogcatcher because I needed something to listen to on the way in to work. I have uninstalled it. But I doubt that is the issue.
I have had these sorts of reboots on my Transformer until the third or fourth Honeycomb update. But eventually they fixed it. I suspected this would happen again.
Considering that dogcatcher one of the most popular podcast apps on the market I suspect that there are many people with no problems using it just fine.
But since I need a podcast listener to be able to use the device as I want to, does anyone without issues have a podcast listener that they use?
2 hours into the last experiment and it died again while sleeping.
So that about sums it up. This procedure might help with some issues Transformer's are having but not all.
Recap. Wiped, cold booted, gmail setup, G+ updated still equals failure.
I love how horndroid 'solved' this issue and then goes on the belittle people who are still having it as 'stupid', and probably their own fault. Horndroid, I appreciate your attempt to contribute, but your attitude and stabbing-in-the-dark protocol is not becoming nor helpful to anyone. Definitive statements pertaining to ONE TF101 device that you own are quite naive, there are several different models, and until you have personal access to each model version you should advertise your 'solutions' as "worked for ME", and understand if it doesn't work with others it isn't THEIR fault..this is not a blanket solution for every device's reboot problems. In fact, I am willing to bet the reboots being resolved by this method are of an entirely different genesis than the reboots that I and others are experiencing (hang-boots).
I hear what you are saying I have the reboot issue as well.
I did a reset before and after and only installed xda HD and ran it for 2 days and got 3 reboots so I did the cold boot and then it did it 2 more times that day. Earlier today I almost couldn't get out of the boot loop, so I wouldn't say its a app problem its something wrong with the firmware somewhere
Sent from my SGH-I897 using xda premium
Some aren't too lazy we just don't want to wipe data after every update. I think i have gotten 4? OTA updates and 2 of them screwed up deep sleep while docked. Guess what the first trouble shooting step was...wipe data. Guess what worked...the next OTA. I don't have time to read through all the different threads on the same subject but are people that flashed through cmw instead of ota having the same issue? My buddy went this route and has no issues.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.
knoxploration said:
Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.
Click to expand...
Click to collapse
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..
luna_c666 said:
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..
Click to expand...
Click to collapse
It's hilarious how you think YOUR problem is the only problem that everyone is experiencing.
For a lot of people, it was the app incompatibility that was causing them issues.
Obviously you think your problems are caused by something different, but that doesn't mean there are different problems caused by other reasons.
While all of you are speculating, at least I've posted a solution(even though it's merely doing a data wipe and cold boot, pretty much common sense) that has been proven to work for a lot of people. I've never claimed it will work for everyone; just those having problems due to app incompatibility.
I'm pretty sure this is an issue with the update itself and all these "fixes" are going to be pointless in a little while when an actual fix is released by Asus.
No matter what battery i have left, if i leave the tablet with the screen off for any length of time (half hour say), the tablet seems to die?
To start it again, i have to long press the power button and the device reboots.
Does anyone know why? Its only started since recent updates.
My N10 is not rooted, and running 5.0.1.
Any help would be appreciated.
I guess no one else has this issue?
I literally go back ten minutes after using the N10, and it has shut down. Only a long press to reboot will bring it back?
Frustrated
sparks7 said:
I guess no one else has this issue?
I literally go back ten minutes after using the N10, and it has shut down. Only a long press to reboot will bring it back?
Frustrated
Click to expand...
Click to collapse
I just bought/ordered a Nexus 10 so I might as well come in here and start talking to people about it. lol
I haven't used a Nexus 10 before but it should be like any other Nexus device. If your tablet is turning off on it's own, first off, pray it isn't hardware related. Hopefully some hardware inside isn't failing on you. But to make sure it isn't software related, I would say use the factory images and do a fresh install. This will set anything that is out of wack straight. If its software related, it will fix it.
Cheers for the reply.
Do you mean a factory reset, and I will lose all my saved stuff?
I'm not very clued up tbh, and only ever update the Nexus when notified.
sparks7 said:
Cheers for the reply.
Do you mean a factory reset, and I will lose all my saved stuff?
I'm not very clued up tbh, and only ever update the Nexus when notified.
Click to expand...
Click to collapse
It's not just a simple factory reset that you do in the settings or recovery. It will wipe your device (Internal storage and all) but it wipes everything including all system files and reflashes everything back to the way you got it out of the box. If you had a software issue and sent it in to get fixed, they would most likely do this. Its safe if you read up on it and know what you are doing. Google gives us the factory images for this reason. Here is an article for instructions. Not used to the Nexus 10 forums so I don't know if they have a dedicated thread for this:
http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/
I'm sure there are some videos on YouTube explaining in depth on how to do it as well. You might want to watch them and get familiar with the process. It's not that hard once you have everything you need to do it. Just back up everything onto your computer, flash the images and put everything back onto your tablet when done.
Thanks very much. I'll have a read up on that and give it a go.
My tablet used to do that. I've had this tablet since I pre-ordered it on initial release (so it's old!) It would also freeze/reboot at times, especially using any browser, so I naturally thought it was a browser problem. But, it would also occasionally do as you describe, wouldn't turn on unless I did a hard reset - holding power button 15-20 seconds or so. I'm also rooted so I started trying different roms. Finally, I flashed the 10.18 release of AOKP. It's beautiful & runs perfect. I've not had ANY, not a single issue & have been running it since last October. I don't think I'll ever change anything from here on. That's just my personal experience.
Sent from my Nexus 10 using Tapatalk 2
Thanks for your help.
I'm going to properly read up on things before I try to resolve it. I don't want to make a mess of it