[Q] Soft Bricked? GS3 Sprint - Sprint Samsung Galaxy S III

So I had to create account just to post my problem before taking any drastic measures. I have been on the XDA forums for a while and I'm not a complete n00b(disclaimer here) when it comes to rooting and ROMing but I done messed up.
So I had this ROM installed which was being a little finicky with the screen. It would flash randomly when either texting or in Facebook. Mostly when the keyboard was up(swiftkey 3). Anyways, I had no real expertise in flashing Kernels so I thought a would give that a try to see if that might help anything.
Went into the forums about intalling custom kernels and came across this thread.
Followed ChaseBroyles steps that he gave, the exact method( this may where I have messed up) then I reboot, it shows the SAMSUNG logo but then turns its self off. So I try to go into recovery, shows at the top Recovery Booting, then shows Samsung Galaxy SIII logo then turns its self off.
So the next logical step is to go into Download mode. It boots into download just fine, then I try to get it to connect to the computer. Tried all of my USB ports and all the cables that I have for Micro USB, still nothing. Odin wont detect it and neither will my computer. I tried removing the battery and letting it sit for a while, and that didn't work either.
So all the help will be apprecited, I do have a jtag but not available to me til this weekend sadly. If that is what I need to do, I'll try that but if I can get it fixed today or sometime this week it would be most appreciated!

Korumaru said:
So I had to create account just to post my problem before taking any drastic measures. I have been on the XDA forums for a while and I'm not a complete n00b(disclaimer here) when it comes to rooting and ROMing but I done messed up.
So I had this ROM installed which was being a little finicky with the screen. It would flash randomly when either texting or in Facebook. Mostly when the keyboard was up(swiftkey 3). Anyways, I had no real expertise in flashing Kernels so I thought a would give that a try to see if that might help anything.
Went into the forums about intalling custom kernels and came across this thread.
Followed ChaseBroyles steps that he gave, the exact method( this may where I have messed up) then I reboot, it shows the SAMSUNG logo but then turns its self off. So I try to go into recovery, shows at the top Recovery Booting, then shows Samsung Galaxy SIII logo then turns its self off.
So the next logical step is to go into Download mode. It boots into download just fine, then I try to get it to connect to the computer. Tried all of my USB ports and all the cables that I have for Micro USB, still nothing. Odin wont detect it and neither will my computer. I tried removing the battery and letting it sit for a while, and that didn't work either.
So all the help will be apprecited, I do have a jtag but not available to me til this weekend sadly. If that is what I need to do, I'll try that but if I can get it fixed today or sometime this week it would be most appreciated!
Click to expand...
Click to collapse
Let me make a summary and you can correct me if I'm wrong:
You had a rooted phone with a custom Rom (JellyBam) and a custom Recovery (CWM or TWRP). Please clarify which Recovery you had (and version, if you remember it). Also, please clarify which version of JellyBam you had installed (latest is 7.6.2).
You decided to flash a new Kernel, thinking it'd help with the random screen flickers. Please clarify which Kernel you flashed.
Now when you try to boot into the Rom, you get stuck in a bootloop (phone doesn't progress past or turns off at the Samsung Logo).
When you boot into Recovery Mode, it gets to the recovery loading screen then turns off.
Download mode works fine, but your computer doesn't recognize it.
You have a JIG.
So it sounds like you flashed a Kernel which was not meant for your Rom. JellyBam is a 4.2.2 Rom, but there are two types of kernels for 4.2.X Roms: those based off of Linux 3.0 and those based on Linux 3.4. After a little searching, I couldn't find which version JellyBam is using, but if it's based off of 3.0 and you flashed a 3.4 Kernel, it'll give you a bootloop. It doesn't exactly explain why your recovery got messed up, but others have had their recovery partition borked by a bad kernel flash, so it's not out of the realm of possibility. Tis is why I want to know which version of JellyBam you had and which kernel you flashed. This will help us know how to help you.
Ok, so your phone is not beyond repair. I'm a little disconcerted that you cannot boot into Recovery, but that happens every once in a while when flashing, so it's not the worst thing to happen. You can, however, boot up into download mode. This is very good. Make sure you have the latest Samsung drivers on your computer and that you don't have Kies installed (Kies has been known to interfere with Odin). See if that works to get Odin to recognize the phone.
If the above works, all you have to do is follow the rooting guide to get a custom recovery back.

Okay so you followed instructions on how to flash a kernel but what kernel did you flash? I think you flashed a kernel for the gsm variant which is completely different than the Sprint kernels. Well if you flashed the kernel he recommended you flashed kt747 Koontz kernel. Which is correct but did you download the correct one? There is one for Touchwiz one for AOSP and there are several for AOSP depending on the romantic and build date. So if you can provide this info it should be easy, but quick way to fix your problem is to just refresh your room right now.
Edit: hats off to Topherk beat me to it...
Transmitted with a portable device using Xparent Blue Tapatalk 2

topherk said:
Let me make a summary and you can correct me if I'm wrong:
You had a rooted phone with a custom Rom (JellyBam) and a custom Recovery (CWM or TWRP). Please clarify which Recovery you had (and version, if you remember it). Also, please clarify which version of JellyBam you had installed (latest is 7.6.2).
You decided to flash a new Kernel, thinking it'd help with the random screen flickers. Please clarify which Kernel you flashed.
Now when you try to boot into the Rom, you get stuck in a bootloop (phone doesn't progress past or turns off at the Samsung Logo).
When you boot into Recovery Mode, it gets to the recovery loading screen then turns off.
Download mode works fine, but your computer doesn't recognize it.
You have a JIG.
So it sounds like you flashed a Kernel which was not meant for your Rom. JellyBam is a 4.2.2 Rom, but there are two types of kernels for 4.2.X Roms: those based off of Linux 3.0 and those based on Linux 3.4. After a little searching, I couldn't find which version JellyBam is using, but if it's based off of 3.0 and you flashed a 3.4 Kernel, it'll give you a bootloop. It doesn't exactly explain why your recovery got messed up, but others have had their recovery partition borked by a bad kernel flash, so it's not out of the realm of possibility. Tis is why I want to know which version of JellyBam you had and which kernel you flashed. This will help us know how to help you.
Ok, so your phone is not beyond repair. I'm a little disconcerted that you cannot boot into Recovery, but that happens every once in a while when flashing, so it's not the worst thing to happen. You can, however, boot up into download mode. This is very good. Make sure you have the latest Samsung drivers on your computer and that you don't have Kies installed (Kies has been known to interfere with Odin). See if that works to get Odin to recognize the phone.
If the above works, all you have to do is follow the rooting guide to get a custom recovery back.
Click to expand...
Click to collapse
To answer your questions in order:
1) I had CWM v 5.x.x I cannot remember correctly. It is the one Zedo max gives in his tutorial. And for Jellybam, I had the latest stable build that was released from their website which is 7.6.2
2) I used this Kernel (http://forum.xda-developers.com/showthread.php?t=1800576) from the thread I stated, another user provided it.
3) Yes that is correct
4) Yes
5) Yes again
6) Yes that is what it is called, bought cause of something dumb I did months ago.
I thank you for the info, it is really appreciated.
So I just updated my Samsung drivers(forgot to do it when I reformatted) and that worked! Odin recognized it and now I'm on the road to recovery!
Thank you so much for my help
So for future reference, what kernel should I install with that ROM just so I don't **** crap up this time?

I wasn't able to find it in the jellybam forums with a brief search, but you could ask over there to see if they can tell you. Also, there are two types of 3.4 kernels, one built before 4/19 and those after 4/19. Make sure you're using the court one.
Hope you can figure it out, and please post back here if you can find it!
Sent from my SPH-L710 using xda app-developers app

I think I might have found a reference to what kernel you're you need to flash: http://www.bam-android.com/forum/showthread.php?3443-Fix-For-D2SPR-7-0-Screen-Issue. From the link, it seems like JellyBam uses 3.0 kernel.
On a separate note. This post might give you direction on fixing the screen flicker issue.
Hope this helps!
Sent from my SPH-L710 using xda app-developers app

Oh, I'm a dolt! You can check your version by going to settings ---> About phone. The kennel version box tells you what version it's running. Look arty mine (from LiquidSmooth):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-L710 using xda app-developers app

Related

Upgrading to GB

Hi all,
I really hope someone can help and I am sorry if I am being an idiot on this but a while ago, I rooted my HTC Desire HD and installed the LeeDroid rom, from this site.
I have had this for a while now and have just decided to upgrade it to Gingerbread so I can install some of the latest rom sets but every time I try to upgrade I get issues:
Downloaded the update via the phone. When it runs and tries to install, it just comes up with a triangle, with an exclamation mark in it and the droid icon next to it. It never gets further than that.
I have grabbed the relevant file from the htc developers site and ran that but it came up saying that it could not update the rom file and to download the right one (triple checked this)
I have done a complete factory reset , so the phone is as was originally.
Has anyone got any idea how I actually get my phone to android 2.3?????
Been out of the phone hack scene for well over a year now so treat me as a newbie if needed lol
I'm pulling my hair out now. Could it be something in the LeeDroid rom set that is causing this?
Thanks in advance to anyone that can help
Shouldnt you get thr gingerbread update from settings>about phone?
Sent from my Desire HD using XDA App
If your rooted let alone running a custom rom you cannot install an ota. If you want gb you can either flash an ruu or my recommendation install a new custom rom
Well eventually tried to install the latest LeeDroid Rom set, which I believed would have gingerbread already packed in to it but it just came up with Installation Aborted all the time.
After many factory resets, my Desire HD now won't boot past the HTC screen at all. I've tried everything but nothing gets me past that point.
Any ideas on this issue or is my phone well and truly bricked now???
Are you able to go into recovery from hboot?
If yes simply download a rom and reflash. Maybe it was a bad download the first time. Or if you have a backup made do that.
If you have no recovery you can flash an ruu or pd98 file from hboot. I made a guide for this just search for threads I've started
Yes I can boot in to recovery but I have a mini SD card in the phone, so I assume I need to get that attached to my pc somehow and pop another rom on it and run install from clockwork yeah?
If that's the case, I have to seriously find the standard SD car adapter from somewhere.
I'll report back later as I have to go out now for the day. Appreciate your patience on this mate.
No need for an adapter. Should have mention this before. Within cwr you have a setting to mount the SD card.(mounts and storage). So you mount it, transfer rom, unmount,then full wipe,maybe also format system,cache dalvik, and flash rom
Exactly what marsdta said. Boot into recovery, but download a rom before that and place it into root of your SD card. From recovery wipe data and cache, select install zip from SD card and off ya go. Initial boot after flashing ANY rim may take 5 or 6 minutes so bear with it. Everything you need to know about proper flashing can be found here, just look.
Sent from my Desire HD using XDA App
OK happy to be looked at as stupid here but how can I transfer a rom to my SD card when it's in a phone that won't boot up????
I assumed I would need to put it in to an SD card adapter and then pop in to my computer.
Are you saying that, once I mounted the sd card in CWR, my computer should see it, even though the phone won't boot???
Correct. Once you mount it in cwr your PC will be able to see it
OK I downloaded, what I considered to be a Stock rom for the HTC Ace, which is also the desire, copied to sd card and then tried to install. This is what I got:
Installing /sdcard/RUU_Ace_Gingerbread_S_HTC etc etc etc.zip
Finding Update Package...
Opening Update Package...
E:Can't open /sdcard/RUU_Ace_Gingerbread_S_HTC etc etc etc.zip (Bad)
Installation Aborted.
Honestly, I thin kI need a direct link to a ROM that should work. :-(
From the looks of it your trying to install a ruu zip from recovery which you can't do. Those are flashed through hboot.(must be named PD98IMG)
if you want the stock feel but without the bloat and better optimized I would say to try cleardroid.
Sent from my HTC Desire HD with Beats Audio using XDA App
OK Popped PD98IMG on to my SD Card and booted to CWR and it automatically picked up on it. It tested the image file for a while, then said loading and then, after about 4 minutes, it went back to the recovery screen.
What now?
Everything I seem to be throwing at this phone either says bad image or Installation Aborted
did you read my last comment? You can't flash a pd98 from cwr.
If you want to go the pd98 route you need to place the file in the root of your SD card.(not in a folder) boot into HBOOT. it will scan and ask to lad it press up to accept
If you're being a **** then you're being a helpful one.
Read my last post too. It's what it did. It scanned the P98 image and then said loading but I got no prompt to accept anything. It quickly says parsing P98IMG then it just goes back to the recovery screen.
I'm only going down the P98 route because that's what a lot of forum threads say is best to do, if you're having issues like mine.
I will try to find the cleardroid one you mentioned and see if that works
You said cwr in your post. That's why I said what I said.
When it fails to parse it could be two things the download was bad or your SD card is acting up. You could try to redownload the pd98 and try again
Just to clarify. Hboot is the white background.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cwr is with black background.
Are you able to enter cwr? Or just hboot
Yes can enter both. White screen to start with and then the black one when I hit recovery.
Would it be a benefit for me to format the SD card via CWR screen and pop the image back on there?
Ok just wanted to make sure we were on the same page as hboot and cwr are not interchangeable.
I was going to suggest that too but you beat me to the punch. Reformat then try the pd98.
I would try a custom rom. But that's just my preference. I forgot what XDA section I was in. Cleardroid is an inspire rom not sure if it will work for.dhd. you van try android recvolution seems to be a popular one. I'm more of a cm fan, so.you can try that if you so.choose
OK I think I will end today, for me at least with a simple question:
Can you recommend a custom ROM that will take me up to gingerbread at least or do I have to do something different to get me there, as I think the LeeDroid one I have is Froyo?
Sorry, wrote this after you had responded

Boot Manager

I just started using boot manager and after some frustration it appears that I have it working now. I was wondering though after booting into a rom from slot 2, getting the settings, sounds, wallpapers, folders, widgets, etc.. setup will all that stay the same after booting into a rom from another slot or going back to the phone rom and then back to slot 2 rom. Thanks for your help.
scott7044 said:
I just started using boot manager and after some frustration it appears that I have it working now. I was wondering though after booting into a rom from slot 2, getting the settings, sounds, wallpapers, folders, widgets, etc.. setup will all that stay the same after booting into a rom from another slot or going back to the phone rom and then back to slot 2 rom. Thanks for your help.
Click to expand...
Click to collapse
Yes, everything you change/mod/add/delete will save to this slot. I have fully customized ROM's running on each slot and I like to use this as an evaluation for new ROM's.
Has any one had any luck getting skyraider zeus to work with BM. It will install to a slot just fine but it won't boot. I do have the force large boot.img checked.
The only way i got Zeus to work was to load onto phone then restore to a slot on boot manager an it will run fine.Sense roms seem to be more tricky to run with boot manager.
I tried installing a nandroid twice and each time it finished the notification said click here for boot options. I clicked it and it just went back to BM and the only option was to stop install. Any ideas?
Don't mean to hijack, but I get an error when installing cm7, when boot manager is making a boot.img. I already set the setting for larger boot.img. Any body got ideas?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Make sure logging is disabled in Superuser settings and make sure to turn on "screen on during install" in Boot Manager settings along with the force large boot.img. If both those settings are set like that and it still won't work just keep trying it will after a few attempts. I have struggled with this app but have stuck with it and now I love it. I started a thread in the General section called, "Boot Manager Discussion", I am hoping to get some user support, tips and tricks started like I have seen in other forums on XDA but for other phones.
RRF12 said:
The only way i got Zeus to work was to load onto phone then restore to a slot on boot manager an it will run fine.Sense roms seem to be more tricky to run with boot manager.
Click to expand...
Click to collapse
can you explain how you did this? I am not sure how to restore to a slot. I would like to have MIUI as my phone rom (since you can't get data as a slot rom) and restore my phone rom (bindroid) to slot 3. I looked under all the settings I could find, but can't seem to find the answer.
thanks in advance!
420fan said:
can you explain how you did this? I am not sure how to restore to a slot. I would like to have MIUI as my phone rom (since you can't get data as a slot rom) and restore my phone rom (bindroid) to slot 3. I looked under all the settings I could find, but can't seem to find the answer.
thanks in advance!
Click to expand...
Click to collapse
Install the ROM like normal, (ie: wipe and install via recovery) set it up like you want, backup, and restore the backup of whatever you want to, start up boot manager, then select this option. "restore nandroid"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So to brake it down, install Rom like normal, make a backup and use that backup to move Rom to a slot instead of being the phone Rom?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
JHumBL3 said:
So to brake it down, install Rom like normal, make a backup and use that backup to move Rom to a slot instead of being the phone Rom?
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Click to expand...
Click to collapse
Essentially yes.
Ok I will try that now
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
tylerlawhon said:
Install the ROM like normal, (ie: wipe and install via recovery) set it up like you want, backup, and restore the backup of whatever you want to, start up boot manager, then select this option. "restore nandroid"
View attachment 869251
Click to expand...
Click to collapse
Thanks a lot, I don't know how many times I have looked for this and went right by it. Trying it now.
Edit: Tried that with a sense rom (bindroid) and it hangs at splash screen. Had to do the two finger salute and get back into recovery. hmm. Got large boot.img checked, any other thoughts?
Still not working but every now and again I will try it again to see if it works.
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Besides checking "force large boot.img", also make sure to check "screen on during install" in boot manager settings. You also need to disable logging in the settings of superuser. It was suggested to me and seems to work, use ext2 instead of ext4 as long as boot manager detects ext2 for the rom you want to install to a slot.
JHumBL3 said:
Still not working but every now and again I will try it again to see if it works.
Sent via My Incredible 2 fully rooted and cookie wasted going 110mph. Imma GeeK it, till it MegaHertz™
Click to expand...
Click to collapse
I had a couple of times the boot process stuck at splash screen. What worked for me, in addition to checking the large boot image, disable su logging, screen on during flashing etc- was choosing ext2, not ext4.
The splash screen lingers a little longer than usual, so be patient for a couple of minutes before giving up and pulling battery.
However, after trying a few roms and although boot manager is really cool, I can't say it is different than wiping, flashing a rom and then restoring other roms from recovery- it takes more or less the same amount of time (and sdcard storage).
Also, I noticed that although I have flashed gasps, after boot it didn't recognize them, Boot Manager doesn't like it (don't know why, maybe some licence check? is this really necessary???). So, to revert back to phone rom I always need to go through recovery and flash boot.zip again.
The same applies if for whatever reason with the booted rom one cannot gain Wifi access or data, then BM won't start, back again to recovery.
IMHO it is just a hassle to use, takes too much time, but is nice if one doesn't like to go too much through recovery, doesn't trust rom manager and so on. Or, if one wants to keep several roms and go back and forth between them.
Sent from my HTC Glacier using Xparent Cyan Tapatalk

Had a buddy root my phone and I have some issues 2.3.6

Had a buddy root my phone because my defy was very slow and clunky. I didnt do it because he has done it a bunch of times on other phones and I had no idea what I was doing.
He first did liquid arc 2.0 and it was AWESOME except when making calls. I couldnt hang up calls...so I had to wait until someone else hung up and then it would drop the call.
I heard great things about cm7 and cm9 so I told him to try those.He but he said it would error everytime he tried those roms?
He then put on 2.3.6 and its OK but for some reason I only get 3G. I also cannot use my camera!?
I told him about these issues and he said there is no way of getting a different rom because its non-down-gradable?
Is the stuff he is telling me accurate? If anyone could help me I would appreciate it. I wouldnt mind this rom if I had 3g and a camera but I would really like CM7 or CM9 but like I said, he couldnt get them to work, unless he is doing something wrong.
Thanks
Is true. He must have tried to flash it like other android phones. Your current ROM is indeed undowngradeable. It's a ROM got the defy+. These have different camera modules as most of the original ones.
You can still instal CM7 you just have to look for defy+ ones (for defy + kernel) but camera will not work.
You should read the threat in dev category that's something like bl6 go to froyo. Don't know it your on a bl6 or 7.
Give the dude a slap on his face and do it yourself now. ;-)
Edit:
Someone in the same situation as you. You can try the solution proposed here:
http://forum.xda-developers.com/showthread.php?t=1485009
Sent from my MB525
Try this. http://forum.xda-developers.com/showthread.php?t=1486731 I stuck at Android 2.3.6. too. Then I flashed this ROM via RSDlite. now everthing is fine again.
OK good...it sounds like it can be fixed.
Customromfan: I would like to give that a try BUT I have no clue on what to do.
I could do a lot of research and probably be able to get it done but since my scenerio is a little different than most step by step instructions could someone please help me on this?
All I do know is I need to download RSDlite but I dont know anything else from there. Heck, I dont even know how to get to the bootloader screen....
Any help would be much appreciated. It sucks being stuck on only the edge network, no camera and the battery life is horrible along with other issues...
He who takes the short path soon stumbles & falls
Here's what I would do ^^
Make your mate buy ph off you 2/3 the $$
Buy another one... ebay or like - & start off slow & do it yourself...
You'll appreciate your ph more & you'll look after it better...
-=or=- drop it in some salt water, for like an hour!! (heard this fubar's defy) Then claim your warranty ;-)
...then start from scratch
Why would I do that when its fixable?
mgp32 said:
Why would I do that when its fixable?
Click to expand...
Click to collapse
:mmm: you could ask the guy that broke it to fix it ^^
Most info: http://forum.xda-developers.com/showthread.php?t=1216982
Stock recovery is when you press power + Vol down (could also be up, don't know) and when you get a triangle press both Vol keys
The root tool = superoneclick (Google is your friend)
To instal CM7 afterwards: search for 2nt init defy apk, put it on you sd card, unable unknown sources in settings> app> dev
Find the apk in an explorer app (if the room doesn't have one, get it from the market) follow instructions, reboot twice. Then press Vol down with blue let, go to custom recovery, wipe data and cache and instal the zip you have put on your sd earlier.
Sent from my MB525
So all I do is flash the ROM that Customromfan posted. Find CM7 and install to SD card(anyone know a good link?). Then install 2nd init. Then go to custom recovery, clear cashe/data and then install CM7?
Anything Im missing? I dont have to re-root right since its already rooted?
Once again this is ALL new to me so the more details the better!
Thanks!
nepotu said:
You've mentioned in the OP that you have flashed the 2.3.6 Full SBF. To get your camera working all you have to do is follow next steps:
1) download this SBF (link); I think it's the same SBF jianbangguo suggested
2) restart in stock recovery(Vol down + power) a do a full wipe (wipe data + cache)
3) restart in bootloader mode (Vol Up+Power)
4) plug in the USB and flash with RSD Lite (v>= 4.9) the SBF downloaded at 1)
5) your Defy should be running on Froyo kernel now.
6) activate USB debugging and root it with SuperOneClick 2.3.3
7) install Defy 2nd init (i recommend you to look for v1.4.2, because this app has all required files in it)
8) download a froyo CEE nandroid backup (SBF's topic, Froyo CEE topic or search for it on Google) and put it on your SD Card
9) restart your phone in custom recovery (Vol Down on the blue [email protected])
10) restore Froyo CEE nandroid
11) do a full wipe (data, cache and dalvik cacke) in custom recovery, then reboot.
Click to expand...
Click to collapse
Fist try the first 5 steps. If it boots, you have your camera back, otherwise please tell. The ROM you are on then is rubbish. It's a Chinese without a market and stuff. To instal a new ROM, you will have to instal 2nt init (this starts up before android to modify it). To do so, look at step 6 and 7. If you want to go back to a stock ROM, follow the next steps. If you want to instal CM7, there are a few options. I am on the cherrypicks version and don't have many bugs. The others won't have them to I think.
Just download the zip and instead of restore the nand, instal the zip. If you want I'll edit the post with links later.
Edit:
For CM7 you can use this one:
http://www.defy-cm.net/jordan-cm7.2-nightly/cm72-120212.0129-NIGHTLY-Defy.zip
(It's from Epsylon3's latest build)
I think you also need to install the right kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=811082&d=1323463612
And the gapps (market and stuff):
http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
So step 10 would be: Press install zip, navigate to the place you placed the files. Install the three (the order doesn't mather).
If you want to restore the nand to go to the original froyo:
http://ge.tt/9Gj23TD Place it in clockworkmod/backup on your sd.
Labsin, I did steps 1-5 and everything is looking good!
Now, Im lost on what to do with 2nd init. Do I download it from the phone or my computer? How do I get it downloaded to the phone? Detailed instructions on these steps would be much appreciated!
Labsin, have you tried miui? Ive heard good things, is this easier to install than CM7...thinking maybe I give this a try...
Thanks again man....thanks to you Im starting to understand this stuff a little bit...
Download latest apk in the Attached Files of the threat. Place it on your sd. On your phone: go to settings>apps>activate 'unknown sources'. Search the apk on your phone and open it (go trough your apps as there will be an app to explorer sd content). When installed, open and follow instructions.
If you want miui, you have to replace the cm7 zip with that of the miui. There are many different versions. WIUI has many languages and didn't have any problems with it:
http://forum.xda-developers.com/showthread.php?t=1161110
You can use that guide to install. No need for the gapps. I suggest however to install te Kernel of my previous post.
I browsed the files on my phone and found 2nd init. I dont see any instructions though?
At this point am I OK to boot into custom recovery and load CM7, Kernal and gapps(the links you provided in an early post) ?
Thanks again...
I think you didn't root it. On phone, go to strings> apps> development> enable 'usb ...". Google for super one click root. Download it, extract it on pc, run it, connect phone, press root.
If you get no errors, reboot the phone.
To instal the apk, you have to get something like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
After that, you can find the app in your appdrawer.
Sent from my MB525
You arent going to believe this........I got it!!!
Now I got another question...how do you get the cool looking clocks and animated weather stuff?
Thanks again labsin and all the others that posted, you guys are awesome!
Update...
I seem to be having the same issue I had with liquid arc. I love the rom so far BUT during a call when I take the phone off my ear it will sometimes not show the screen where I can hang up. I try hitting the top power button but it still won't. It will only "come back to life" when the person on the other end hangs up. So in other words if this decides to happen when someone doesnt answer I have to pop out the battery otherwise I would be leaving a LONG message.
any help on this would also be appreciated. Ive searched and searched but it seems no one else is having this issue.
mgp32 said:
Update...
I seem to be having the same issue I had with liquid arc. I love the rom so far BUT during a call when I take the phone off my ear it will sometimes not show the screen where I can hang up. I try hitting the top power button but it still won't. It will only "come back to life" when the person on the other end hangs up. So in other words if this decides to happen when someone doesnt answer I have to pop out the battery otherwise I would be leaving a LONG message.
any help on this would also be appreciated. Ive searched and searched but it seems no one else is having this issue.
Click to expand...
Click to collapse
flash MIUI
Do you have a link for miui? Any other files I have to flash (gapps or anything).
To go to miui would I just have to put the file on my SD card, go into custom recovery, clear date/cache, and then flash the miui file?
No need to re-root or do anything else right?
Edit: Its getting ridiculous now...even when the other end hangs up it stays locked most of the time and I have to reboot
Thanks for any help...
Have you flashed to kernel I posted earlier?
http://forum.xda-developers.com/attachment.php?attachmentid=811082&d=1323463612
It's the kernel that's used for the liquidArc. Seems not to go well with the kernel of the bld6 kernel you installed to downgrade. Just install it in custom recovery. No need to wipe this time.
If you want to go to MIUI:
WIUI is a spinoff with about the same looks but with tweaks that are specific for the Defy. It also packs with many languages. MIUI(en.miui.com) is only in Chinees and MIUIAndroid (http://miuiandroid.com) translates it only in English.
There are really a lot of sites that translate MIUI and add tweaks (galnet,...)
The steps are as you describe. If you get a blue let when you power on your phone DONT install 2nt init again. If you have a superuser app, you are already rooted. LiquidArc is rooted stock.
Info for WIUI:
http://forum.xda-developers.com/showthread.php?t=1161110
Edit:
Just checked, WIUI contains gapps and kernel so you only have to download the zip (and maybe addons you want) place them on your sd and install them. And wipe data/cache
As long as you flash without a low battery or don't let your pc crash when you flash a sbf and don't flash a bld 7 sbf. You will not be able to brick it
Just flashed 2.1.20 MIUI....
Only played with it for a couple minutes but it can do the main thing a phone should do and that is being able to hang up a phone call(atleast so far...)
I did notice it is only showing "e" when I should be in "3G"....is this rom not capable of picking up 3g?
Labsin- I did flash that kernal you suggested. Later today Ill probably try flashing again and just adding the gapps....

[Official] One Stop FAQ Thread - Noob Friendly (All questions go here)

As the title says this will be a one stop for ALL your questions related to Sprint Epic 4G Touch (SPH-D710). Please use this thread.
This thread is completely noob friendly. :angel: Please no trolling or flaming. Any posts insulting or trolling fellow members will be reported promptly. Use
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
button. Don't abuse it. We don't want our moderators to waste time. Also no general chit chat please. We want this thread to be as helpful as possible so less clutter is better
Ask ANY question related to root, kernels, recovery, any roms, battery issues etc.
Don't think that if you post your question in this thread it won't get answered. If you feel an urge to start a "new" thread for each question thinking that people will answer that quickly or something like that then you are mistaken. Don't worry and ask away here!
No one person is responsible if your phone becomes a shiny black brick..Neither me nor anyone answering question.
Any one can answer questions and point users in the right direction.
Although it is encouraged to search and research before asking, I can understand that maybe you feel overwhelmed by your search results and just want to make sure before you do anything stupid or are just confused by all the answers you find
_____________________________________________________________________________________________________________________
Oh and about the search function. Some tips. There are different ways to do a search on Xda.
-Site wide search which is on the top right corner and looks like this -
This search is useful for apps and such which are not necessarily device specific.
-Another search option is to search within the forum for example search in "Epic 4G Touch Q&A". This will search all threads created in this forum. It looks like this right above the threads.
-Third search option will show up where you see the option above when you are in a particular thread. It is the most useful when you are in a ROM thread an looking for some help specific to that rom.
_____________________________________________________________________________________________________________________
Goal here is to stop repeatedly asked questions in Q&A forums AND have all the questions in one place. Chances are high that the issue you are having was already experienced by someone else and the answer is somewhere in the forums.
Post 2 will have all the common questions/answers. New FAQs will be added as I come across something noteworthy.
Post 3 will have all the questions/answers that other members have asked. I will link to posts from within the thread here so you don't have to go looking for them.
Please let me know about any errors or recommend changes. I am all ears.
________________________________________________________________
Thanks to all whose threads I have linked below.
General Q&A
Ok here we go: Most common questions. I will be adding more from time to time.
Q. How do I root my phone?
A. The safest and easiest way to obtain root is to use one of the stock Odin one clicks. They are all found here. That thread has all versions listed. You want to use the one-click for the version you have. There are 2 versions. No data version will save all your user data. Use that only if you need to root your current version. Not recommended when downgrading versions.
Alternate Method:-
This is not recommended for first time users. Its a bit complicated but not hard.
-You need the EL26/29 kernel with CWM(linked below), CWM SuperSU zip, and stock kernel for the build you are on. By stock kernel, I mean for example if you are on unrooted ICS FL24 then you need the FL24 Stock kernel in a zip format. All these files need to be on your SD Card before you begin. All files can be found at rwilco12.com.
-Flash the EL26/29 kernel first using mobile odin kernel slot or desktop odin PDA slot.
-Boot into recovery.
-Flash zip from internal/external SD card.
-Find the SuperSU zip file and flash it.
-Now remember to not reboot. Flash the stock kernel zip.
-Now you can reboot.
Phone will boot up and you are still completely stock but rooted with NO CWM.
Q. Now I am rooted, how do I install clockwork mod (CWM) recovery to flash new ROMs etc? Oh did I mention flash ANY ROM? ICS or JB.
A. There are several ways to do this and need to be careful in choosing the right version. If you are not using a safe recovery then you may brick your phone. More on bricks later.. Before you install cwm you need to decide why you want cwm recovery. Are you just looking to install CWM recovery so you can flash a new ROM? If So.. Follow those steps to be as safe as you can get with flashing new roms.-Make sure you have the ROM zip file already on your SD Card before starting this. Gapps too if it is a CM/AOKP/AOSP based rom.
-Download Mobile Odin Lite from here. You can also download from play store.
-Download GB - EL26 Stock repacked with CWM from here. You want the .tar.md5 file. OR use EG4T-EL29-directbootCWM-v3.tar.md5 md5 - 2b781e4515982a6b7d9586cbb3158647. Direct boot kernel will boot into recovery after flashing in mobile odin.
-Open Mobile Odin and select the kernel slot. Find the file on your sd card and select it.
-Flash firmware. It will take few seconds and phone will reboot.
-Next step is very important..
-Now one thing to keep in mind here is that you just flashed a Gingerbread based kernel. If you are on ICS or JB, your phone will no longer boot. So you want to hold down power + vol up until you see the CWM recovery.
-From here on follow the instructions of the rom you are trying to install.​Only follow the above process ANY time you need to flash a new rom.
Any new rom you flash comes with its own recovery which are generally safe to flash different mods etc for that particular rom.
You can also use desktop odin to flash the kernel but it will trigger a yellow triangle and show a flash count which shows how many times you have flashed something custom.
Q. Now that I have my favorite ROM and its all setup... How do I make a nandroid backup?
A. Simple.. Just go to recovery that the rom came with by holding down vol + power up OR most roms have the reboot to recovery option in the power menu. Once in recovery go to backup and restore. Go to backup and let it run. It will take few minutes to complete. Also avoid changing names of these nandroid backups because that could cause MD5 mismatch and you won't be able to restore it.
A nandroid backup is a FULL backup of your phone. It comes very handy if you want to go back to your setup when trying new roms.
Now off to brick related questions.
General advise:- Please please please read the directions of the rom you are trying to flash and ask if you are not sure before you regret making a mistake.
Q. I flashed something (lets say you were on some ROM and decided to try a new kernel) and now all I have is a Samsung boot logo and my phone is stuck on it for few mins...
Am I bricked?? Did I brick it for good?
A. In most cases, No. If you see the Samsung boot logo then you are lucky and what you likely have is "Soft" brick. You can recover from this. You can do different things to fix this. If you are not sure and do not feel confident and just want to get your phone working to take a breather, follow this..
-Download EL29 rooted Odin one click to a pc. (you should always keep a copy on your pc)
-Put your phone into Odin download mode by holding power + vol down until you see a screen asking you to press vol up to continue.
-Open the one click .exe file.
-Plug your phone into your pc using an usb cable.
-Wait for drivers to install if you don't already have. Be patient.
-You should see COM:XX where XX is port number. Doesn't matter what number. Now be patient and wait a min or 2. (Sometimes I have seen the COM:XX disappear and then comeback due to some driver reloading..)
-Press start and wait for the flash to complete. *DO NOT UNDER ANY CIRCUMSTANCES MOVE YOUR PHONE AROUND THAT THE CABLE COULD UNPLUG.
*MAKE SURE BATTERY HAS GOOD CHARGE.
*MAKE SURE PC DOESN'T RESTART.
*If the process is interrupted, you will brick your device for sure depending on where odin was in the flash process and it will be hard to fix it or impossible.​-You should wait till phone reboots by itself. Device can be unplugged then.
Another thing you could do to recover from a soft brick is just go into recovery and restore your nandroid backup that you had created.
Q. Ok so now what is "hard" brick?
A. To explain it in simple words.. if you get a flashing blue led and nothing on the display, cannot go into odin mode or recovery then you have a hard brick. For more info refer to this thread and this thread
User Questions
Q: I want CWM which will run with my current version of stock rom. I don't care about EL26 kernel w/cmw. Where do I get it?
A: First of all, I don't see why you would need a kernel with cwm if you are on a stock rom. There is no use as the kernel is not considered safe to perform most functions. But if you still want it.. You can get it here - [KERNELS][CWM][ODIN] Kernel Repository - Download Them All Here and flash it using mobile odin as described in post 2.
Q: I am running AOSP/AOKP/CM based rom and my data is slow. Also my 3g/4g is not working. Oh yeah and I never get a GPS lock. I don't want to go back to stock touchwiz! Please HELP!!!
A: Well you can't update profile and prl using AOSP/AOKP/CM based rom and it has to be done from touchwiz based roms. But there is some good news. You can temp boot to stock EL29 rom and do whatever you want to such as use dialcodes, update profile/prl etc. Temp boot means that you will be able to boot 1 time to EL29 and then next time you boot, you will be back on whatever rom you were on. Follow this simple video to do this.
Also you can try different modems which you can flash in CWM or ODIN. Get them here- [MODEMS][CWM][ODIN] Modem Repository - Download Them All Here
Q. How do I disable the annoying OTA update notifications? They always comeback even after clearing the notifications..
A. It is very easy. Thanks to an apk or a zip created by rocket321 you can disable them permanently. Here is the quote and the post..
[How-to] Disable OTA updates on Stock + Rooted ROMs
rocket321 said:
1. Download FOTAKill.apk and copy to your Phone/SD
2. Use a root explorer (such as ES Explorer) to copy the file to /system/app
3. If the update already downloaded, delete it from /cache
4. reboot
*Credit for the apk goes to the CM team and or whoever creates the gapps packages!
Alternate method if you have a custom recovery:
1. Download the Disable.OTA.Updates.zip file and flash in CWM (this will install fotakill and clear cach for you)
*Thanks to tdunham for alternate method!
Click to expand...
Click to collapse
Q. There are so many modems and with the JellyBean leaked modems, things got real confusing. What modems can I use with which ROM?
A. Just remember one thing. With the leaked JB stock samsung builds and custom TouchWiz ROMs based off of these leaked builds, you can ONLY use the leaked JellyBean modems. These leaked JellyBean modems will NOT work with ANY previous GB and ICS builds or AOSP JellyBean ROMs.
Note:- You CANNOT flash any modem using the EL29 directboot kernel.
This **** needs to be stickied.
Sent from my SPH-D710 using xda premium
Hey BluesRulez, you might want to add the descriptor for our phone describing for the newb what it is and is not. That the Epic 4G Touch is Sprint USA's version of the Samsung Galaxy SII (Model SPH-D710). What I mean is at least a couple of times a week we see someone who has flashed an international version of a ROM or kernel and borked their phone.
Thanks for the work and contributions. Hope more will come and contribute and more importantly read this too.
Current problem: My girlfriend woke up to realize that her alarm hadn't gone off and her phone was locked up tight and wouldn't respond to anything. After a battery pull, it would only boot to the splash screen.
Background: Her phone has only been flashed a couple of times. She was on Calk 2.8.1 and 2.9 almost forever. Odin one click for a fresh start before going to Recaulked 1.8. (w/ included Agat 5.4 kernel). Version 1.9 had just come out, but was based on a leak and had warnings about bootloops, so we went with 1.8. After a couple of weeks she started having problems when trying to do almost anything, it would try to open the clock. It would also freeze up. She removed clock and installed a 3rd party clock. She started having the problem again. She kept putting off my request to install alogcat.
What has been done so far: Two finger salute into recovery, tried to run a backup. It failed to mount system. I tried a recovery. It stuck at writing system. I had to battery pull. USB jig does put it into download mode. I have stopped there. It sounds like the system partition (or part of it) is borked. This phone has not had a flashhappy life.
Best way to proceed?: Should I find an unrooted stock to odin to and visit a sprint store? I know Vanberge bricked on the Agat 5.4 kernel and read most of that thread back a while. 1.8 was still current when it was flashed and it was the last thing that was flashed, so there hasn't been anything to call MMC_CAP_ERASE. Nothing had been flashed since the beginning of September.
As a recap, this phone has never had anything on it but stock, Calk, and ReCalk. All help will be appreciated.
Edit: I am not blaming anyone for anything. I am trying to decide how to go forward. If it was just bootlooped, I would have Odined and flashed to a newer version of the ROM. With the problems that our phones have had and the fact that it doesn't seem to want to mount "system", I decided to ask before moving forward. I know repartitioning is possible. If there is a way that a developer can learn more about the problem since it is still in pre-permabrick state, let me know.
I originally posted this this morning in the Re-Caulked thread. at:
http://forum.xda-developers.com/showthread.php?p=33218365#post33218365
I just copied and pasted to here. I think that ReCalk 1.8 is based on FH13? but will have to double check.
If a mod would like to delete the other duplicate post, please do. I am not trying to spam the boards.
Thanks to any and all who help.
Followup: My girlfriend started to have the clock issue again with her new phone. Once again, it never happened when I was there. After asking her all sorts of questions, she mentioned vlingo. It ended up being her charger at work. There was a bent pin and it tried to put the phone into dock mode. Long term use must have shorted the usb port. Her phone was charging (with a good cable) when it was locked up. I don't know exactly how this caused it, but at least there is some explanation now.
driftinganomaly said:
Current problem: My girlfriend woke up to realize that her alarm hadn't gone off and her phone was locked up tight and wouldn't respond to anything. After a battery pull, it would only boot to the splash screen.
Background: Her phone has only been flashed a couple of times. She was on Calk 2.8.1 and 2.9 almost forever. Odin one click for a fresh start before going to Recaulked 1.8. (w/ included Agat 5.4 kernel). Version 1.9 had just come out, but was based on a leak and had warnings about bootloops, so we went with 1.8. After a couple of weeks she started having problems when trying to do almost anything, it would try to open the clock. It would also freeze up. She removed clock and installed a 3rd party clock. She started having the problem again. She kept putting off my request to install alogcat.
What has been done so far: Two finger salute into recovery, tried to run a backup. It failed to mount system. I tried a recovery. It stuck at writing system. I had to battery pull. USB jig does put it into download mode. I have stopped there. It sounds like the system partition (or part of it) is borked. This phone has not had a flashhappy life.
Best way to proceed?: Should I find an unrooted stock to odin to and visit a sprint store? I know Vanberge bricked on the Agat 5.4 kernel and read most of that thread back a while. 1.8 was still current when it was flashed and it was the last thing that was flashed, so there hasn't been anything to call MMC_CAP_ERASE. Nothing had been flashed since the beginning of September.
As a recap, this phone has never had anything on it but stock, Calk, and ReCalk. All help will be appreciated.
Edit: I am not blaming anyone for anything. I am trying to decide how to go forward. If it was just bootlooped, I would have Odined and flashed to a newer version of the ROM. With the problems that our phones have had and the fact that it doesn't seem to want to mount "system", I decided to ask before moving forward. I know repartitioning is possible. If there is a way that a developer can learn more about the problem since it is still in pre-permabrick state, let me know.
I originally posted this this morning in the Re-Caulked thread. at:
http://forum.xda-developers.com/showthread.php?p=33218365#post33218365
I just copied and pasted to here. I think that ReCalk 1.8 is based on FH13? but will have to double check.
If a mod would like to delete the other duplicate post, please do. I am not trying to spam the boards.
Thanks to any and all who help.
Click to expand...
Click to collapse
If you can go to download mode then flash the el29 odin one click.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
If you can go to download mode then flash the el29 odin one click.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
So, you don't think that the inability to mount /system will be an issue?
driftinganomaly said:
So, you don't think that the inability to mount /system will be an issue?
Click to expand...
Click to collapse
You tried to run a backup in recovery and that's when you saw that error. Not sure what you exactly mean by that. Making a backup at this point is useless IMO.
Sent from my SPH-D710 using xda app-developers app
I also tried to restore a backup. That is why I was concerned is that it wouldn't mount the system when I was trying to restore. I have seen people talk about custom pit files because of part of a partition being borked. From what I read, it seemed, further flashing could destroy more of the file system.
Edit: I tried to do a backup, because it had been a while since one was done, and if I could do a backup, I could look into possibly extracting anything important that my girlfriend needed. That part wasn't really important, I just included that I had attempted it for thoroughness.
driftinganomaly said:
I also tried to restore a backup. That is why I was concerned is that it wouldn't mount the system when I was trying to restore. I have seen people talk about custom pit files because of part of a partition being borked. From what I read, it seemed, further flashing could destroy more of the file system.
Edit: I tried to do a backup, because it had been a while since one was done, and if I could do a backup, I could look into possibly extracting anything important that my girlfriend needed. That part wasn't really important, I just included that I had attempted it for thoroughness.
Click to expand...
Click to collapse
In that case I would recommend you read this thread. Has much more info there. Discussion thread for /data EMMC lockup/corruption bug
BluesRulez said:
In that case I would recommend you read this thread. Has much more info there. Discussion thread for /data EMMC lockup/corruption bug
Click to expand...
Click to collapse
Thanks, that is one of the threads that I was planning on reading into more post homework. I think that I only made it through 30 or so pages of that thread a couple of months ago. I haven't been able to stay current on all the info, so I asked hoping someone would be able to point me in the right direction. Have a good evening and thanks for the help.
Bump!!!
This deserves a bump to the top...hopefully it will become a sticky soon....
Very nicely done BluesRulez!
PS.... Moble ODIN is the bomb!!!!
Well I don't understand why people don't ask here?? If folks don't start using it, I might just ask mods to delete this.. there is no point to keep this...
Sent from my SPH-D710 using xda app-developers app
Don't do that bluez. I wish I had this info when I started out. Sometimes it takes awhile to generate traction. Did you pm the mods?
Sent from my SPH-D710 using Tapatalk 2
third son said:
Don't do that bluez. I wish I had this info when I started out. Sometimes it takes awhile to generate traction. Did you pm the mods?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
No. Going to wait few days.
Sent from my SPH-D710 using xda app-developers app
OK Well don't be discouraged. You put a lot of thought and effort into this valuable thread. Please don't remove it. I will link to it anytime I can.
lol good concept to have one thread but kinda pointless when there a whole section dedicated to q & a that is also noob friendly.. good try tho .. agreed for the one guy that did post his issue.. just go into dl mode and flash el29 one click.. your phone clearly didnt get hit with the eMMc bug since you not hard bricked and you werent flashing something and the phone was just sitting
Sent from my SPH-D710 using xda app-developers app
Old age creeping up on me, I could've sworn that MiguelHogue posted here already about the battery spin test. LOL
We need a section for 'My battery life is horrible' please.
How to check your battery... is it the battery or the rom... is it an app or is it the battery (run stock for a while to be certain).
I always lead off with:
As our phones are getting older, I've been seeing a lot of battery failure issues. If your phone battery is over 10 months old, more than likely it is time for a new battery.
Lately, I've also been seeing a ton of power button failures too btw. All those users holding their power buttons down to boot into recovery I bet. Lately, I've been getting into the habit of only using the software solution to boot into recovery since most extended toggles include it on custom roms. If I'm running without extended toggles, I always download the app 'Quickboot'. It saves from having to press and hold our aging power and volume buttons down while waiting for the recovery screen to pop up.
tdunham said:
Old age creeping up on me, I could've sworn that MiguelHogue posted here already about the battery spin test. LOL
We need a section for 'My battery life is horrible' please.
How to check your battery... is it the battery or the rom... is it an app or is it the battery (run stock for a while to be certain).
I always lead off with:
As our phones are getting older, I've been seeing a lot of battery failure issues. If your phone battery is over 10 months old, more than likely it is time for a new battery.
Lately, I've also been seeing a ton of power button failures too btw. All those users holding their power buttons down to boot into recovery I bet. Lately, I've been getting into the habit of only using the software solution to boot into recovery since most extended toggles include it on custom roms. If I'm running without extended toggles, I always download the app 'Quickboot'. It saves from having to press and hold our aging power and volume buttons down while waiting for the recovery screen to pop up.
Click to expand...
Click to collapse
Lol there is that battery thread I took over in general section too. Smart people figure out the problems and people with issues don't act smart and don't use resources available.
Sent from my SPH-D710 using xda app-developers app

Looking For some Guidance

Hello my Fellow s4 users,
Let me start off by saying I am looking for a little guidance here. I am fairly comfortable with rooting, modding, NANdroiding, Flashing, bricking, unbricking, following instructions and using the search button. I am a little dumbfounded on some of the issues I am having.
The issues seem to be isolated to touchwiz based roms only. GE and AOSP ROM's are not part of this problem.
My problem is that anytime I flash a TW based rom (For Example: The little Minions Rom, Infamous, or Wicked), which flash just fine, upon loading or the first time System UI always crashes. I click ok and let the phone sit for about ten minutes to settle. I reboot, and go through the setup wizard ( I have also done it where I skip the setup wizard altogether, with the same results.)
At this point everything is ok.
Until I try to do anything else. I experience extreme Lag, problems with apps Like the phone and Contacts, Titanium Backup is simply non-functional.
So at this point I assume it is user error.
So I Odin back to stock, run triangle away and start fresh.
I repeat this process, and root using the CF-Auto root, and reflash a rom with the same result.
The only thing I can think to do at this point is ODIN back again and try a different Root method.
Does anyone have any ideas or input?
Personally, I'm running Infamous S4 4.0 ROM w/BioShock 1.0 Kernel and 3.1.1 3Minit Framework. Have not experienced the issues you're describing though. You seem to have taken many of the appropriate steps to attempt to solve your issues.
The steps I'd do and some stuff I'd look at, whether related to your issues, and/or tried already are:
- if using TWRP Recovery 2.6.0.0, flash TWRP 2.5.0.2.
- if not already, format card, if 64gb, to Fat32, as some ROMs won't run ExFAT.
- Full Wipe and ODIN Samsung Stock Firmware.
- Save files needed and Full Wipe, including device memory, as you may have a conflict with certain files.
- with Infamous S4, it has Root, so it's not necessary to root via CF-AUTO-ROOT, but can't hurt I guess. CF-AUTO-ROOT is my preferred choice for rooting.
- Uninstall and reinstall TiBu if having issues after doing the above.
- Sometimes when there are issues after flashing ROMs, wiping Cache and Dalvik cache can rectify many issues.
- make sure running appropriate Kernel for the M919. Appropriate Radio goes without saying, although most ROMs don't have the Radio cooked in because the wrong Radio can Hard Brick.
Anyway, I'm sure I missed something which may turn out to be the Golden Challis :laugh:, but the above hopefully will help.
As a note, and possibly to get more feedbackffrom the source, you can post your inquiry regarding Infamous S4 in thetthread as all are extremely helpful, and the Developers offer excellent support. The same with Minions, as they are part of the Infamous Team. I don't run Wicked ROM but have heard excellent feedback, and their support appears to also be excellent.
Feel free to copy this post if you'd like to post it in Infamous S4 thread, as there'll be others to expand on my response
OP:
What phone?
What baseband?
What recovery?
I am M919 tmobile
MDL
CWM.
...and have no issues with Wicked 5.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-M919 using Tapatalk 4 Beta
Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
Sent from my SGH-M919 using xda premium
ODIN Recovery tips
3r0k said:
Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
You may find TWRP 2.6.0.0 the cause of some issues, and that 2.5.0.2 will resolve them.
I'll post some ODIN Recovery tips, if you should need them:
Here's the TWRP 2.5.0.2 file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
Install with ODIN.
Steps to follow........
Method #1 -
Place file in PDA box*
Uncheck all other boxes.
Press start.
When installation is complete, unplug usb cord and pull the battery.
Insert the battery but Don't turn on the phone.
Place phone in Recovery mode via the Power + Volume up buttons.
Method #2 -
The other way I've read to install TWRP Recovery is:
Place the TWRP 2.5.0.2 tar in the PDA box*
Check the auto reboot box and f time reset box.
Start the installation and let the phone reboot.
I believe the above method is the method of choice, but sometimes the Recovery doesn't take, so Method #2 above is recommended.
Here is an explanation why:
http://forum.xda-developers.com/showpost.php?p=41166759&postcount=28
Gunkk said:
OP:
What phone?
What baseband?
What recovery?
I am M919 tmobile
MDL
CWM.
...and have no issues with Wicked 5.1.
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
everything same as you except Im using twrp.
There's your sign...
Sent from my SGH-M919 using Tapatalk 4 Beta
Ok, getting home in a bit will keep you guys updates. thanks for the help.
3r0k said:
Ok, getting home in a bit will keep you guys updates. thanks for the help.
Click to expand...
Click to collapse
Sounds :good:
ODINing 2.5.0.2 I think will solve your issues.
Wipe cache and dakvik cache after booting into Recovery and prior to booting system.
If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.
Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed
Biker1 said:
Sounds :good:
ODINing 2.5.0.2 I think will solve your issues.
Wipe cache and dakvik cache after booting into Recovery and prior to booting system.
If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.
Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed
Click to expand...
Click to collapse
Yea, still gettting errors.
Even tried to switch to CWM, and that had issues with backing up.
Looks Like I am gonna ODIN Back and full wipe.
3r0k said:
Yea, still gettting errors.
Even tried to switch to CWM, and that had issues with backing up.
Looks Like I am gonna ODIN Back and full wipe.
Click to expand...
Click to collapse
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.
ODIN TWRP 2.5.0.2 and you should be good to go.
If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.
20m all together;
Firmware.
Recovery
ROM/Kernel
Infamous S4 Roots you, so hopefully you'll be up & running i nno time.
Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.
In your case, TWRP 2.5.0.2 only was worth a shot
Biker1 said:
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.
ODIN TWRP 2.5.0.2 and you should be good to go.
If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.
20m all together;
Firmware.
Recovery
ROM/Kernel
Infamous S4 Roots you, so hopefully you'll be up & running i nno time.
Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.
In your case, TWRP 2.5.0.2 only was worth a shot
Click to expand...
Click to collapse
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.
3r0k said:
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.
Click to expand...
Click to collapse
If you:
- did a Full Wipe
- ODINd Samsung Stock Firmware
- ODINd TWRP 2.5.0.2 Recovery
- checked your ROM download
- Flashed your ROM (with Kernel cooked in)
- Wiped cache and dalvik cache
and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.
Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.
Biker1 said:
If you:
- did a Full Wipe
- ODINd Samsung Stock Firmware
- ODINd TWRP 2.5.0.2 Recovery
- checked your ROM download
- Flashed your ROM (with Kernel cooked in)
- Wiped cache and dalvik cache
and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.
Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.
Click to expand...
Click to collapse
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.
3r0k said:
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.
Click to expand...
Click to collapse
At this point the only thing I can suggest is to:
- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.
I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.
I then come back to the issue and say, 'Hmmm, how'd I miss that?'
And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'
I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.
Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.
Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.
And you say this only happens on Touchwiz roms?
What about the stock touchwiz after you odin back to stock? Does that give you similar problems?
If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
And you say this only happens on Touchwiz roms?
What about the stock touchwiz after you odin back to stock? Does that give you similar problems?
If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
Stock ROM works great.
Wicked is now working and running great also.
I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.
I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.
Biker1 said:
At this point the only thing I can suggest is to:
- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.
I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.
I then come back to the issue and say, 'Hmmm, how'd I miss that?'
And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'
I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.
Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.
Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.
Click to expand...
Click to collapse
No apology needed, you have by far been the most helpful.
Maybe Ill just wait for a new build to come out and go from there.
Maybe Ill possibly look into a log cat to send the Dev. I dont know if the log can catch the errors in my process but maybe.
3r0k said:
Stock ROM works great.
Wicked is now working and running great also.
I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.
I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.
Click to expand...
Click to collapse
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?
If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.
If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?
If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.
If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
If I did restore any other system data it would be coming from other touchwiz ROMS, however I am not. The problem is at least on the ROMS I am having difficulty with I cant get far enough to reinstall TiBu anyways. The systemUI crashes immediately as soon as the setup wizard loads, then when I get to the Wi-Fi password screen, the settings force close and the Setup Wizard starts all over again.

Categories

Resources