Develop Bugs

Help!!!! Please ASAP

My Evo was rooted but now it will not finish a reboot It's Repeating that Sprint 4G animated screen. Please tell me theres a fix.

rvajuggalo said:
My Evo was rooted but now it will not finish a reboot It's Repeating that Sprint 4G animated screen. Please tell me theres a fix.
Click to expand...
Click to collapse
You're bootlooping, pull the battery out.
To solve the problem you need to boot into recovery, hold power + vol down
From there revert whatever changes you made. It would be helpful to know just what you did to get it to bootloop.

If you made a nandroid backup, flash that . Hold vol down and reboot into recovery.
Sent from my PC36100 using XDA App

nenn said:
If you made a nandroid backup, flash that . Hold vol down and reboot into recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Got it back!! now back to my OG issue 4G and Wifi seem to not be right.

rvajuggalo said:
Got it back!! now back to my OG issue 4G and Wifi seem to not be right.
Click to expand...
Click to collapse
its the exact same thing from when you made the backup, so then it wasnt right before you did it.
flash some custom roms and enjoy

What file will i need to flash the all the radios back to stock? or is there a way?

unless you flashed a radio update the radios shouldnt be touched with the rom flashing. they should be stock.
my baseband number which should be stock since i dont remember flashing anything is
1.39.00.05.31

[Q] How did my recovery change?

So, strangely enough, I went to boot into recovery this morning and my rogue hit man recovery got changed to the CWM 5.8.1.5. I definitely did not flash that and had to troubleshoot it because it would keep booting to that recovery. I got it fixed but why would it get changed without me flashing it? I am running Caulkin's Rom and have not done anything with the recovery since I flashed it. Some advice on how to avoid this is the future would be nice. and I am not using Rom Manager

ryandoubleu said:
So, strangely enough, I went to boot into recovery this morning and my rogue hit man recovery got changed to the CWM 5.8.1.5. I definitely did not flash that and had to troubleshoot it because it would keep booting to that recovery. I got it fixed but why would it get changed without me flashing it? I am running Caulkin's Rom and have not done anything with the recovery since I flashed it. Some advice on how to avoid this is the future would be nice. and I am not using Rom Manager
Click to expand...
Click to collapse
I'm a flash-a-holic, and have come across a couple of Kernels that have their own recovery versions included. Off the top of my head, Phoenix and Siyah come to mind. If you recently flashed a Kernel, there is your answer.
Not sure what else could have caused your issue, but it will be interesting to see what other members have to say.
tneS morf ym yxalaG II S (777i-HGS) gnisu ADX muimerP.

...
I have not flashed any kernels or recovery other than rogue's hitman. The phone just reverted back to CWM 5.8.1.5 again. I may try a new rom after I reflash the rocovery

Stop using hitman! Its bricking phones right now because somethings wrong with the original touch recovery. Switch to an old rouge recovery right away.
Sent from my SPH-D710 using XDA App

...
MrDowntown12 said:
Stop using hitman! Its bricking phones right now because somethings wrong with the original touch recovery. Switch to an old rouge recovery right away.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
OK, thanks.
It has done soft bricks on my phone when I go into recovery it would go to the CWM 5.8.1.5. At that point the recovery would keep rebooting to that recovery without letting me control it. I found that if you hit the home button a bunch of times it would boot back into the ROM, just fyi.

MrDowntown12 said:
Stop using hitman! Its bricking phones right now because somethings wrong with the original touch recovery. Switch to an old rouge recovery right away.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
+1,00000000 on this. Avoid hitman like a fat kid avoids salad. I don't know why that mod is still active.
tneS morf ym II S yxalaG (777i-HGS) gnisu ADX muimerP.
Click link below to read XDA Rules. Only takes a few minutes.
http://forum.xda-developers.com/announcement.php?a=81

Need help please

Hi i used the wrong recovery to backup my Samsung epic touch and now all I get is a blue light it won't start or boot to recovery or odin any help will be appreceiated. I'm using EL26 kernal to flash ICS roms I went to cwm touch recovery instead of rouge recovery and now I'm stuck.
I do also have the FE02 plus recovery I forgot to mention that with having all my stress.

Sounds like another hard brick... Your only small hope would be in a usb jig and then a jtag service, but both might fail and you now have an expensive paperweight.
Sent from my SPH-D710 using Tapatalk 2

Try the manual method to get into download mode (copied from sfhub's TAR posts):
Code:
Method #1
Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode
Without getting into download mode you're probably a victim of the eMMC lockup. But to know for sure, what kernel version were you on when you last tried a CWM restore or wipe?

I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
BTW it won't go into download mode

bigdaddy619 said:
I was using EL26 kernal. I should have booted into recovery manually but I used rom manager it booted me into cwm touch instead of rouge recovery. I was going to flash a new ICS rom so I wiped everything and formated system and when I pressed reboot recovery, and rather then just going back it froze so I waited a bit then pulled the battery that's when it wouldn't do anything except the blue light.
Click to expand...
Click to collapse
OK, the behavior - specifically that the phone froze and wouldn't respond until you pulled the battery - matches the eMMC lockup. Unfortunately yours appears to be locking up during the boot process which is why you can't get to download mode. Only way to fix is to take to Sprint for replacement.
Still curious how you did it though - and let's try our best to find it so that others don't suffer the same fate:
bigdaddy619 said:
I used the e4gtauto file to flash FE02+recovery. Which I understand is the one you need if you are flashing ICS roms but i used cwm touch before I realized it was the wrong recovery it was to late.
Click to expand...
Click to collapse
Can you link to the post containing the file you used to flash? I'm not aware of an FE02 build - maybe Agat's FF02 repack? And can you also include source of CWM touch if from a different ROM?

Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT

shiftr182 said:
Sounds like he used CWM Touch on an ICS build. It flashed the recovery through rom manager, but the recovery isnt built correctly for our phones. Its a hard brick and will need to get a replacement. YOU HAVE TO USE A GINGERBREAD RECOVERY FOR IT TO WORK RIGHT
Click to expand...
Click to collapse
Yea even then he stated fe02? Isnt that an ics kernal and also used touch which neither is good for flashing a new rom.. either way people make mistakes and like said already you have a nice paperweight.. to sprint you must go lol
Sent from my SPH-D710 using XDA

http://forum.xda-developers.com/showthread.php?t=1342728 this the link where i got the e4gtauto.
If you want CWM use Option C in the Auto Root Package to install EL26+CWM (you are already rooted so Option A is not necessary)

OOOOOPS it was the FD02+recovery sorry

bigdaddy619 said:
OOOOOPS it was the FD02+recovery sorry
Click to expand...
Click to collapse
There's your culprit. Once you get it replaced you'll want to stick with GB or FF02 repack which was done with care to avoid triggering the lockup for now. Sorry you had to find out this way...
Sent from my SPH-D710 using XDA

Close please
Sent from my MB855 using xda app-developers app

where did you find cmw touch?
I've been looking all over for it!

emottau said:
I've been looking all over for it!
Click to expand...
Click to collapse
Looking for what?
Sent from my MB855 using xda app-developers app

[Q] Tmo T989 doesnt reboot correctly

when i hit reboots it will go through, vibrate once and show the samsung logo and black screen and it doesnt power on.
had this issue with different roms.
anyway to fix???

Try TDJ's Darkside cache wipe script in the development section
Sent from my SGH-T989 using Tapatalk 2

VoiD_Dweller said:
Try TDJ's Darkside cache wipe script in the development section
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
already did, used it before flashing each rom, i got this phone brand new last week too

AngryDinosaur said:
already did, used it before flashing each rom, i got this phone brand new last week too
Click to expand...
Click to collapse
Using it before flashing isn't particularly helpful. Use it when you have the boot issue, like now.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

What recovery are you using? Please include the version too.

RTFOP said:
Using it before flashing isn't particularly helpful. Use it when you have the boot issue, like now.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
will try it

Afeety said:
What recovery are you using? Please include the version too.
Click to expand...
Click to collapse
used the toolkit to root and flash recovery
v5.0.2.6 for recovery
on JB miui right now

AngryDinosaur said:
used the toolkit to root and flash recovery
v5.0.2.6 for recovery
on JB miui right now
Click to expand...
Click to collapse
Try using TWRP 2.22
Sent from my SGH-T989 using xda premium

you may be semi-bricked. Just try a gingerbread rom or something.

AngryDinosaur said:
already did, used it before flashing each rom, i got this phone brand new last week too
Click to expand...
Click to collapse
So you did this before the flash.. Do this.. Pull the battery, insert the battery, turn phone on and boot it into recovery (not into ROM) and flash the cache wipe script.. See if that works.
Am I correct in you saying the roms work and it just doesnt reboot properly?

ya when i hit reboot it vibrates once to power off but then it will vibrate one more time and show the samsung logo and black screen, need to pull battery to get out of it

Mine was doing the same thing, I installed "Quick boot" from the market, and that works everytime

idbl_fanatic said:
Mine was doing the same thing, I installed "Quick boot" from the market, and that works everytime
Click to expand...
Click to collapse
Doesn't quick boot do basically a hot reboot? Where the phone actually is not turned off but more or less just restarting the ui?
sent from my BAD A$$ Epic touch

patrao_n said:
Doesn't quick boot do basically a hot reboot? Where the phone actually is not turned off but more or less just restarting the ui?
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
No, you can do shut down, reboot, recovery, boot loader, and hot boot.

idbl_fanatic said:
No, you can do shut down, reboot, recovery, boot loader, and hot boot.
Click to expand...
Click to collapse
ill try quick boot too then

Mine did that too when I first installed a cm9. I did a complete wipe from cwm (dark side super wipe because I was on non-touch) then reflashed my recovery (flashed twrp via cwm) and it stopped having issues and not one since.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Isn't the CWM supposed to be updated to 5.0.2.7?

I just updated to the newest CMW, and I no longer have this problem, also, my "root going away" problem has been fixed as well.

idbl_fanatic said:
I just updated to the newest CMW, and I no longer have this problem, also, my "root going away" problem has been fixed as well.
Click to expand...
Click to collapse
I switched from CWM to TWRP and the problem went away.
I still has the issue with CWM's 6.0.1.4 recovery.

d01100100 said:
I switched from CWM to TWRP and the problem went away.
I still has the issue with CWM's 6.0.1.4 recovery.
Click to expand...
Click to collapse
Cwm 6.0.1.4 works for me I just prefer twrp. Moral of the story if you flash a recovery and have issues rebooting to it check the md5 (should do this with anything you flash) and re-flash in case it was a bad download or bad install.
Cwm when flashed from Odin always gave me issues until I did a dark side and reflashed.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Only have download?

Hey, I rooted my GS3 and installed cm10, but it was very buggy so I tried to reflash stock. As of right now I can get into download mode and that's it. I tried reflashing stock but idk if I'm doing it right.

How are you doing it?

dietryiin said:
How are you doing it?
Click to expand...
Click to collapse
Thanks for the quick reply! Through Odin, I've managed to hear the start tmobile sound but the screen stays black.

I'm not really sure what the problem is, but did you use the correct stock rom for Tmobile? And you did it through the download mode by holding down button, home, and power right? Just making sure it wasn't clockwork or twrp.

Barrett S said:
Thanks for the quick reply! Through Odin, I've managed to hear the start tmobile sound but the screen stays black.
Click to expand...
Click to collapse
Did you do a factory reset in recovery?

dietryiin said:
I'm not really sure what the problem is, but did you use the correct stock rom for Tmobile? And you did it through the download mode by holding down button, home, and power right? Just making sure it wasn't clockwork or twrp.
Click to expand...
Click to collapse
I uses the unrooted, plain old tmo firmware. Yes, I see the "Downloading, do not turn off target!!" message.
bigtom624 said:
Did you do a factory reset in recovery?
Click to expand...
Click to collapse
I am unable to access recovery.
If I could get to CWR I'd be okay.

I flashed an insecure boot and now it just stays at the glowing samsung logo.

That's one of the reasons flashing back to stock can be hard. Try flashing the stock image that is injected with a custom recovery (cwm I believe) found in the developers section.
Wiping during this operation is crucial so as not to get stuck in a boot loop
Sent from my SGH-T999 using xda premium

Android_Monsters said:
That's one of the reasons flashing back to stock can be hard. Try flashing the stock image that is injected with a custom recovery (cwm I believe) found in the developers section.
Wiping during this operation is crucial so as not to get stuck in a boot loop
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
How do I wipe it from download mode?
Where do I find this file? I always flash them separately.

In the stickies in the developer section
Root no tripping the flash counter
Sent from my SGH-T999 using xda premium

Barret,
Be patient. Wait for 3-5 minutes after boot.
Once it's done, see this --> http://forum.xda-developers.com/showthread.php?t=1999922

Thanks everyone, here's how I fixed it:
I flashed the stock rom without auto reboot and then pulled the battery.
Then, I flashed CWR without auto reboot and pulled the battery again.
After that, I could get into CWR so I flashed cm10 and a different google apps package than last time.
I don't have any cm10 bugs now. It would crash acore alot and stock apps like messaging wouldn't work.
Thanks for the help everyone, I'm set now.

Barrett S said:
Thanks everyone, here's how I fixed it:
I flashed the stock rom without auto reboot and then pulled the battery.
Then, I flashed CWR without auto reboot and pulled the battery again.
After that, I could get into CWR so I flashed cm10 and a different google apps package than last time.
I don't have any cm10 bugs now. It would crash acore alot and stock apps like messaging wouldn't work.
Thanks for the help everyone, I'm set now.
Click to expand...
Click to collapse
Do you know what was wrong with the first Google apps package that you flashed? Did you get the 4.1.2 one from goo.im?
-Sent from my Nexus 7.-

phositadc said:
Do you know what was wrong with the first Google apps package that you flashed? Did you get the 4.1.2 one from goo.im?
-Sent from my Nexus 7.-
Click to expand...
Click to collapse
Yeah, that's the one I used. Dialer, contacts, and messages would crash immediately and process.acore would stop responding constantly.
I tried Defy GAPPS instead and that worked.

Barrett S said:
Yeah, that's the one I used. Dialer, contacts, and messages would crash immediately and process.acore would stop responding constantly.
I tried Defy GAPPS instead and that worked.
Click to expand...
Click to collapse
Weird isn't the one from goo.im the one that most people use? I wonder what went wrong with yours.
-Sent from my Nexus 7.-

phositadc said:
Weird isn't the one from goo.im the one that most people use? I wonder what went wrong with yours.
-Sent from my Nexus 7.-
Click to expand...
Click to collapse
Idk, I flashed CM and then the goo.im apps. I'm sure I had the right ones.