Develop Bugs

HELP! I rooted my phone and not touchwiz is gone

Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!

Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!

Thanks Already started doing that waiting for it to download now

Still no touchwiz... great!

Try flashing a stock rom via clockworkmod.

efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.

I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.

efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.

dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....

I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.

Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha

[Q] Calkulin's Rom won't allow recovery..

So I I've had 2 different recoveries so far that have worked fine.. both came from Rogue though. One was from the 1.5 kernel (Hitman) which installed CWM Touch recovery, the other came with the normal recoveries based off CW 5.0.2.7. They were working fine until I installed Calkulin's Rom(2.8.1). Not sure if they're just incompatible or what, but when I go to recovery it shows the background image of the recovery but none of the options show up. It shows for about half a second and then it goes back to the original boot screen, then to the 2nd screen and turns on. So it basically skips right through the recovery and reboots. Do I need a new Rom or can I fix this? I really like the battery life and visuals of Calkulin's Rom and would love to be able to keep it.
EDIT: One more thing.. Since I installed the ROM, I've been getting market error 492. It doesn't allow me to install anything in the market..
I haven't tried a full wipe yet, so I guess I'll try that and then see how that works with the recovery and Rom..

I did the same thing to my phone this week, and I'm running Blazer, so i'm sure it has nothing to do with either ROM.
Not sure how I caused it but with so many folks running both without this error, I'm guessing that your issue (like mine was) was probably some how self induced.
I flashed back to stock and started over, and things have been working great. Might be worth a shot flashing back, or restore a backup and start fresh.
Haven't seen the market error before. I'm sure someone here has
Good Luck

If you got it off here, could you show me which stock you flashed..?

Everything you need is in the Epic 4G Touch Android Development section
Here is the post I used from Sfhub
http://forum.xda-developers.com/showthread.php?t=1433101
Watch the videos by Qbking77 They walk you thru everything step by step. (I hear his video intro rif every time I close my eyes now so you've been warned) Makes it super easy.
I would read everything you can and watch the videos before you get in too deep. I've had this phone since December, and just flashed my 1st ROM this week cause I've been reading up, and learning all I could before I jumped in the pool.

Well I've done all this with 2 phones before but I've never had this happen.. normally I just get the Rom and I'm good to go..

I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.

premo1 said:
I think I must've gone wrong somewhere when I originally rooted through a stock rom.. It already seems to be more respondful.
Click to expand...
Click to collapse
Try booting while holding the volume up and power button.
If that does not work, flash recovery from rom manager, and that should get you into recovery to flash whatever kernel/recovery u want.

I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..

premo1 said:
I've done all that.. None of it works.. I'm currently ODIN'ing Factory Stock Rom with root. Hopefully after that I can redo all of these and eventually end up with a working, corresponding Rom and kernel..
Click to expand...
Click to collapse
Good Luck.

Recovery and market are now working Thank you Adanorm!

Glad your back up and running

[Q] Need Advice...Blank Screen after loading LK 1.6

Hello everyone,
been creeping the forums for the past week...new to the android world but i find the idea of customizing your phone in your own unique way was a good enough reason to leave blackberry after using it for 7years. Anyways....onto my real problem here.
(I appolgize in advance if i mess up the terminology. hopefully you can understand me)
I use a phone on wind mobile (SGH-T999V) and from what i know it's been a safe assumption that if the T999 works then the t999v will most likely work.
I was on AOKP build 5 prior to flashing to the CM M2 ROM...used odin to install CWM_Touch 6.0.1.2.tar then did the steps in
http://forum.xda-developers.com/showthread.php?t=1946701
Edit : I forgot to mention...I can get the screen to go into recovery mode...however, when i press up on the volume key my phone will turn itself off.
and i plugged the phone in again and it decided to be read by my computer.
to install the ROM which worked successfully... however this is where I think i messed up or maybe it has nothing to do with it at all... But my MMS messages did not work so i tried to just play around with some settings and i searched the forums and tried the things that were posted but to no avail. One of the things i did try was to uncheck the privilege unknown applications button and to turn off developers option so USB debugging should be off...or it may have been on...not too sure.
Anyways, so i remembered that I haven't finished the last 2 steps from the "how to flash a rom" in the midst of reinstalling my programs using titanium backup. So i reboot into recovery mode(and this is where i messed up i think) and i wiped my factory data again so after noticing that i did that i went back and restarted the phone and filled in all the information on the welcome screen again. and went back into recovery.
did "wipe cache partition" 3 times AND dalvik cache once then proceeded to install from my sd card the "lk_aosp_jb_tmo-v1.6". After installing i rebooted the device again and i get to see the Samsung Galaxy S3 screen and my screen will go completely black. However, I know it's still on as the battery charging indicator is on and my two buttons around the home button are lit up constantly....out of curiosity i decided to call myself using a land line and the phone is still working (I hope this is good news and that i'm not bricked but teased in a sense i can't fix the screen).
I tried to plug my phone in and it didn't detect it so i reinstalled the drivers and it did detect the phone. I laoded the Samsung Galaxy S3 Toolkit V.2.3.0 in hopes of trying to recover via option 6 "backup and restore your phone" and was hoping to revive it by restoring the nandroid backup however when i typed in my folder the toolkit crashed on me...and now it can't detect my phone as when i try to install the drivers again - the MDA driver seems to fail everytime.
Sorry for the long message...I wanted to be detailed in a sense I don't have to keep giving people more details... your help would be appreciated...Thanks everyone!!

Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Sent from my SGH-T999 using xda premium

You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Sent from my SGH-T999 using xda app-developers app

Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1845836
It was 1.6 as of yesterday when i downloaded it but it looks like it's 1.7 now. That was my original plan however when i boot into recovery i literally have roughly 1second to pick an option before my screen goes blank again. I tried to boot it a few times into recovery trying to "beat" the blank screen but that hasn't worked.
You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Click to expand...
Click to collapse
Yeah the problem is I can't get back into the cwm as my screen goes blank
I tried to find a link for the stock kernel but the 2-3 that i found all have 404.
Something tells me i just ran into bad luck with the kernel flash. or does it have to do with me doing a wipe/data reset again and perhaps not selecting the debugging options/trusting unknown apps checkbox before running it through again? I'm not sure...just grasping at straws here to why my phone is doing that.
Anyone else have more ideas?? Anything will help...Thanks again!!

Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium

mt3g said:
Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay - I'll try it tonight when i get home from work. Here's where my lack of knowledge/noob status comes into play. Thanks for the help.
Do i get into Odin via trying to start my phone in download mode? (I tried to hold the power button/down/home) but that's when i get that glimmer of hope before my screen turns blank again when it asks if i want to continue or reboot my phone.
Or do i try to get it running through Samsung Galaxy S3 Toolkit V.2.3 ?? (If that's the case can you tell me which option i should use to get to the appropriate screen? or should i just launch the odin executable file? (however I'm not sure how that would get anything accomplished if my phone doesn't enter download mode...or maybe it's in download mode when i press up on the volume key but the screen is actually blank? Or maybe i don't understand the process 100%)
But lets say hypothetically speaking I manage to get Odin working. Which proper kernel should i be using? I tried looking for the stock kernel but all the links i found 404'ed. Does anyone have one that works? I'm just kind of trying to get my phone working in general...even if it means going back to stock everything. Pointers Anyone?
Thanks!!
Edit: Forgot to mention the fact that I may not be in debugging mode as i tried to turn that off to see if that had anything to do with my inability to send out MMS msg's as i mentioned in my first post... so that might stop me from using Odin no?

Update
Ok well just an update in case it happens to someone else - I pretty much left the phone alone and didn't touch it for 16hrs. Came home from work and it decided to boot up recovery mode so i just wiped data/cache quicker than a little kid wanting to open Christmas presents on Christmas day when they wake up... Needless to say I didn't bother testing the lk 1.6 kernel so i'm not sure if it works with CM10 running a SGH-T999V (Wind Mobile) phone. I'm trying to think of what may have happened and I'm thinking MAYBE it's because i was charging my phone from 20% all the way to about 95 then decided to plug it into my computer ...so maybe an overheat issue?
Anyways. Thanks for everyone's attempt to help. Much appreciated!

Soft brick please help!

Hey guys, I am pretty knowledgeable on flashing rom's as I have done it quite some time now, but I just flashed this rom and can't get my phone to fully reboot. I am not sure if this is supposed to happen or if it is semi bricked etc. I had cyanogenmod 10.1 on my samsung galaxy 3 sprint and I factory data reset, wiped cache, wiped dalvik cache, and format system all before I flashed this Axis rom. I went through the aroma installer and everything checked out and after installation completed it said Installer status: 0 and option for reboot. I hit reboot thinking everything checks out and the phone tries to reboot as I see the samsung logo..but then it goes black....nothing happens for minutes (I am not sure if it is supposed to take that long but it looks completely off..screen isnt on or nothing) so I wait for long time and nothing...I try to turn it on again and samsun logo appears with the Cyanogenmod Blue Android guy...(not sure if that is the same logo used for axis or if it didnt wipe the logo from previous rom)...then it goes black again...so i tried reflashing the rom again and again...and nothing same results..just turns on samsung logo with the blue man and shuts off...i am able to get to the custom recovery...but thats it...please help...I do have a nandroid backup but when i go to restore it doesn't find it...is there anyway to get another rom or something flashed? maybe through odin etc..

I think something like this happen to me before. I ended up having to go back and use Odin and reinstall the recovery and rom. Some how I had erased the ability to install a ROM. I may have had to treat my phone like it was the first time rooting it and go through the entire root process. Sorry just working from memory. Hope this helps and good luck

i wasnt aware that we had a rom called Axis for this phone. you probably flashed a rom not meant for our model phone

That rom is for the AT&T model, why would you flash it to a sprint model? I think using Odin to go back to stock might be your best bet.

metalfan78 said:
That rom is for the AT&T model, why would you flash it to a sprint model? I think using Odin to go back to stock might be your best bet.
Click to expand...
Click to collapse
It is a universal rom supposedly they have every carrier on the aroma installation im actually having this same problem he is :/ it sucks phone just keeps rebooting and wont stay in recovery or the download mode for long

I never trust those multi-carrier roms. Doesn't seem safe to me for this exact reason.

Thisismyringtone said:
It is a universal rom supposedly they have every carrier on the aroma installation im actually having this same problem he is :/ it sucks phone just keeps rebooting and wont stay in recovery or the download mode for long
Click to expand...
Click to collapse
you must have gotten a bad download then. check the md5sum to see if thats the problem
metalfan78 said:
I never trust those multi-carrier roms. Doesn't seem safe to me for this exact reason.
Click to expand...
Click to collapse
same here i dont trust those multicarrier roms. i just stick to the ones dedicated especially for ours.

acostaae90 said:
Hey guys, I am pretty knowledgeable on flashing rom's as I have done it quite some time now, but I just flashed this rom and can't get my phone to fully reboot. I am not sure if this is supposed to happen or if it is semi bricked etc. I had cyanogenmod 10.1 on my samsung galaxy 3 sprint and I factory data reset, wiped cache, wiped dalvik cache, and format system all before I flashed this Axis rom. I went through the aroma installer and everything checked out and after installation completed it said Installer status: 0 and option for reboot. I hit reboot thinking everything checks out and the phone tries to reboot as I see the samsung logo..but then it goes black....nothing happens for minutes (I am not sure if it is supposed to take that long but it looks completely off..screen isnt on or nothing) so I wait for long time and nothing...I try to turn it on again and samsun logo appears with the Cyanogenmod Blue Android guy...(not sure if that is the same logo used for axis or if it didnt wipe the logo from previous rom)...then it goes black again...so i tried reflashing the rom again and again...and nothing same results..just turns on samsung logo with the blue man and shuts off...i am able to get to the custom recovery...but thats it...please help...I do have a nandroid backup but when i go to restore it doesn't find it...is there anyway to get another rom or something flashed? maybe through odin etc..
Click to expand...
Click to collapse
During the aroma installation does it have you select a carrier type? And does it have you select a kernel?
Sent from the future via Tapatalk 4

XxSilent.NightmarexX said:
you must have gotten a bad download then. check the md5sum to see if thats the problem
same here i dont trust those multicarrier roms. i just stick to the ones dedicated especially for ours.
Click to expand...
Click to collapse
yeah im not going to trust them again im doing an odin flash now hopefully that works and fixes it
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
edfunkycold said:
During the aroma installation does it have you select a carrier type? And does it have you select a kernel?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
It has all the carriers and you choose sprint and i think the kernal is ziggys if i remember correct

After flashing with Odin. I don't have root anymore which is fine but it just randomly reboots it seems like it reboots when it gets overwhelmed with things well for me anyways so yeah hmm

Well i found out it wasnt anything i flashed after all it was just my power button was sticking and turning it on and off woo thank god hah but yeah so not sure if OP figured his out but that was mine so far ha thanks all for the help

Issues With Kernels

Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel

Anyone ever have this problem?

over16bit said:
Hi there!
I have a bit of a problem with my T-Mobile S4 and I was wondering if there was anything I could do to remedy the situation. So here is the problem;
Two days ago, I was playing PPSSPP and then I saved the state so I could eat lunch. When I came back to play, I loaded the state and then all of the sudden, my screen jumbled for a split second then went black. I tried to restart my phone, but it would always boot up and then go back to a black screen. I then reinstalled my ROM and was able to use my phone again. Thinking that it was over, I decided to re-flash my kernel. But then, it happened again, only this time, I could kind of turn my screen on but it was all messed up. See photo below. I re-flashed my ROM once more, made a titanium backup of my apps and then proceeded to wipe my whole phone through TWRP, going to wipe -> advanced wipe and then selecting every check box except for external sd and USB otg. Afterward, I re-flashed my ROM once more, booted my phone to make sure it worked then flashed the kernel same thing happened. SoI tried a couple different kernels but they all produced the same results. Just a jumbled screen. What could have went wrong? And is there a chance I can fix it?
ROM used - ParanoidAndroid 3.99 RC2
Kernel used - KT-SGS4
Other Kernels tried - Chronic Kernel, Blue ROM kernel
Click to expand...
Click to collapse
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT

alloycowboy said:
I have never heard of this problem. It seems you have tried your best to fix it...
My suggestion is to go back stock and see if the problem is still there. If it is then its a hardware problem.
If its not...re-root and flash a rom and go from there.
Sent from a Insane S4
SICK MADE DEVELOPMENT
Click to expand...
Click to collapse
This...but use Odin to go back to stock. Dont' just try to flash a stock ROM.
REALLY reset it hardcore by using Odin to flash the stock firmware package in its entirety.

That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!

over16bit said:
That's what I was thinking about doing, but I can't download the stock image. The download never completes. I've thus far tried to download from the hotfile mirror and from stockROMs but they're always slow and never complete. What I'd really like is a torrent, but if anyone knows of any other mirror or what might be going wrong, I'd appreciate a point in the right direction.
Thanks!
Click to expand...
Click to collapse
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app

Flash the 10.16 AOSP 4.3 build of KT's kernel. Any build newer than that is for CM based ROMs compiled AFTER 10.20.

alloycowboy said:
You need to use your pc to DL the firmware....it will fail trying to from your phone.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.

over16bit said:
I am trying to download it from my PC. :/
Also, I tried the earlier KT kernel as that was the one I had on hand. Same thing happens.
Click to expand...
Click to collapse
Sounds like hardware problem. I hope im wrong.
Let us know how it goes after you odin back to stock
Sent from Insane S4
SICK MADE DEVELOPMENT