Develop Bugs

Please delete thread.

Just installed Rom Manager messing around and found that our device is listed but when I tried to flash it's recovery it shows 5.0.2.6 installed, but when I boot into recovery it's still showing 5.0.2.3.
Was it already listed and just not working? I'm running Starburst 1.7 with the stable kernel if it matters.
Sent from my SPH-D710 using xda premium

poppygt said:
Just installed Rom Manager messing around and found that our device is listed but when I tried to flash it's recovery it shows 5.0.2.6 installed, but when I boot into recovery it's still showing 5.0.2.3.
Was it already listed and just not working?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No, it wasn't listed previously.
Probably the first stages of giving us official support.

I never installed it before because it was easy enough to use Odin and I knew we weren't supported when I got my device. That's cool though because I had read he was gonna nail down recovery and pass the phone onto the team for development. Nice step in the right direction.
Sent from my SPH-D710 using xda premium

mattykinsx said:
No, it wasn't listed previously.
Probably the first stages of giving us official support.
Click to expand...
Click to collapse
Exactly. Koush writes cwm and he is supposed to be our dev for cm7 too.

I flashed it from rom manager. It didn't work. I tried booting into recovery by turning off the phone and using volume up and power and it brought up stock recovery but then gave me a "!" Error. I also tried booting into it through rom manager with the same results.
Sent from my Samsung Galaxy S II Epic 4G Touch

Has anybody successfully flash cwm from rom manager or boot into recovery from rom manager?

This is good news! Koush is obviously working on support. Cool!
Samsung Galaxy S II

I tried flashing... And pushing the files but always seem to boot into the old recovery i had... But this means that he or teamhacksung will work on cm7 when its done
Sent from my SPH-D710 using XDA App

deano0714 said:
I tried flashing... And pushing the files but always seem to boot into the old recovery i had... But this means that he or teamhacksung will work on cm7 when its done
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Still good because rom manager allows you to select quick backup and restore which speeds thing up.

I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium

mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Really? Still didn't work for me... I just went into rom manager, flashed cwm and then selected reboot into recovery and when it rebooted I got the box with the arrow then the triangle with the "!" In it.
I'm fully stock(kernel and rom) just rooted.
Sent from my Samsung Galaxy S II Epic 4G Touch

Worked great I formatted usb and ad storage, odined the new recovery, and flashed the new recovery through rom manager by selecting download recovery, after it downloads click install rom from sd, go into clockwork folder/downloads and select the new recovery, choose wipe dalvik and Ok. It boots into recovery, flashes, performs back ups seems to be fully functional so far. Thanks Koush! You daMan, may we please, respectfully request some CM7 bits? Been waiting a year and half to get some bacon again. (had the OG Epic previously)
Sent from my SPH-D710 using XDA App

mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same exact thing happens to me!
Sent from my Samsung Galaxy S2 Epic Touch 4g using Tapatalk

mauricehall said:
I have sussessfully flashed with rom manager. I can boot into recovery from a cold boot but if i do reboot to recovery from rom manager it will start to flaash something amd stop a quarter ways... I made a bold move and did a battery pull and it booted into recovery fine from the cold boot
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Instead of pulling the battery, I held the power button until the phone rebooted in CWM itself.

What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!

musclehead84 said:
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Midnight rom with lostkernal
Sent from my Samsung Galaxy S2 Epic Touch 4g using Tapatalk

musclehead84 said:
What kernel are you guys on that this worked for?
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Chris' pulled stock with cwm, although the version now up has some problem-wait until he fixes it. I'm using the first version.

move_over said:
Chris' pulled stock with cwm, although the version now up has some problem-wait until he fixes it. I'm using the first version.
Click to expand...
Click to collapse
And you can confirm cwm updated? Does the version in cwm show 5.0.2.6? Or does it still show 5.0.2.3? When I try to flash over compleatly stock kernel it doesnt work, it says it flashes but I cant get into cwm. When I flash over chris' stock with cwm packed it appears to flash just like on the stock kernel but when I load cwm it shows the older version 5.0.2.3. I have tried everything I can think of and no matter what, 5.0.2.6 doesnt load up for me.
Sent from my Samsung Galaxy S II Epic 4G Touch

graffixnyc said:
And you can confirm cwm updated? Does the version in cwm show 5.0.2.6? Or does it still show 5.0.2.3? When I try to flash over compleatly stock kernel it doesnt work, it says it flashes but I cant get into cwm. When I flash over chris' stock with cwm packed it appears to flash just like on the stock kernel but when I load cwm it shows the older version 5.0.2.3. I have tried everything I can think of and no matter what, 5.0.2.6 doesnt load up for me.
Sent from my Samsung Galaxy S II Epic 4G Touch
Click to expand...
Click to collapse
Same for me rom manager says i have 5.0.2.6 but when i boot into recovery it shows the older version

Chris's CWM now shows up as 5.0.2.6,and rom manager can reboot into recovery
Sent from my SPH-D710 using Tapatalk

Help Please

Didn't the instructions for reverting back to completely stock used to be stickied at the top of the development section. If not can someone point me in the right direction to make it back to stock to see if i can resolve my GPS issues.
Thanks,
E4GT
Calks 2.8

http://forum.xda-developers.com/wiki/Samsung_Epic_4G_Touch/ROMs
You can use Odin to flash any tar at the top or buy mobile Odin pro and use it to flash tar and your flash count won't go up ..the pro will root it when it flashes then you can flash a kernel with CWM and not have yellow triangle....I keep it on my phone as it's a way back from bricking when phone won't connect to computer in Odin
Sent from my SPH-D710 using xda premium

Thanks, what is this flash count you speak of?

If you hold down Vol and power button when the phone is off ...it will put you in download mode it will ask you to hit Vol up to confirm it is the number of flashes done with Odin it will say custom firmware or something and have a number ... On earlier bootloaders this could be cleared by using a jig, but they have said later ones can't it's a way for sprint or Samsung to know if you flashed your phone ...mobile Odin does not make the number go up ...
Sent from my SPH-D710 using xda premium

Awesome back on stock and gps locks instantly. Is there a rom that the gps will still work reliably with or do you think I just had a fluke previously.

tw
most of the tw roms work just as good as the stock , if you flash cm7 over the stock it works great

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] Did I soft-brick my GSIII?

I've searched relentlessly for a solution to this, but I haven't come up with anything, so it's time to ask for help.
I just used mskip's Galaxy S3 QCOM Toolkit v2.3 (http://forum.xda-developers.com/showthread.php?t=1746682) to flash CWM and root my GSIII. The recovery flashed successfully, using "recovery-cwm-lte-sgs3-v5.tar" included with the toolkit.
CWM recovery works. However, when I tried to boot the phone, I got the first Samsung splash screen, then the screen turned black, a second later the boot tune played (with no splash screen showing), and then... nothing. The blue notification light blinks infinitely, and the phone is unresponsive except for holding the power button down for 10 seconds, which restarts it, and the same thing happens again.
I can boot into CWM recovery, as well as download mode. I tried wiping the cache and doing a factory reset, which changed nothing. However, when I tried to flash a stock ROM (again using the toolkit), I got an "unsupport dev_type" error. I presume that USB debugging has been defaulted to disabled now from this, but maybe I'm wrong. In any case, I'm not sure where to go from here. I don't want to claim that I've bricked it yet, when I have both recovery and download, but I don't know what to do now.
Help?
EDIT: I'm sorry, I forgot basic information : I'm using a SGH-T999 (T-Mobile GSIII).

I would defiantly boot in to cwr and do a clean install on a diferent rom. Not a back up u made with cwr but a .zip rom... n u sgould b ok.. I would try jb smooth
Sent from my SGH-T999 using xda app-developers app

See if you can flash CM10, if you don't have to have stock.

kipster3001 said:
I would defiantly boot in to cwr and do a clean install on a diferent rom. Not a back up u made with cwr but a .zip rom... n u sgould b ok.. I would try jb smooth
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Looks like the toolkit installed an older version of CWM. I flashed 6.0.1.2 via ODIN (http://forum.xda-developers.com/showthread.php?p=30806933) and then flashed CyanogenMod 10.0.0. Works great.
Thanks so much!

Jacooni said:
Looks like the toolkit installed an older version of CWM. I flashed 6.0.1.2 via ODIN (http://forum.xda-developers.com/showthread.php?p=30806933) and then flashed CyanogenMod 10.0.0. Works great.
Thanks so much!
Click to expand...
Click to collapse
Glad you had it resolved. Another method would have been ODIN back to stock.
Sent from my SGH-T999 using xda app-developers app

[Q] Kernal Flash Messup

I am trying to upgrade my phone from ICS to JB. I flashed Stock GB27 through the odin one-click and every loaded/booted fine. Now I wanted to flashed tdunham's rom "Recalked in Jellybean". In order to flash the rom I have to use EL26 or EL29 cwm kernel to flash it. I used the odin one-click of EL26_Stock_CWM5 (Christ 41 G) and it rebooted. But now it is stuck at the boot screen with a yellow triangle. I'm not sure really what to do at this point to fix it. I've found videos online but they all show the phones going past the boot screen to actually get rid of it.

Cabhills said:
I am trying to upgrade my phone from ICS to JB. I flashed GB27 through the odin one-click and every loaded/booted fine. Now I wanted to flashed tdunham's rom "Recalked in Jellybean". In order to flash the rom I have to use EL26 or EL29 cwm kernel to flash it. I used the odin one-click of EL26_Stock_CWM5 (Christ 41 G) and it rebooted. But now it is stuck at the boot screen with a yellow triangle. I'm not sure really what to do at this point to fix it. I've found videos online but they all show the phones going past the boot screen to actually get rid of it.
Click to expand...
Click to collapse
Reboot into recovery by holding down power button and volume up. That will get you into cwm. From there, wipe data, cache, dalvik, and flash rom. Reboot, enjoy
Sent from my SPH-D710BST using xda premium

jdsingle76 said:
Reboot into recovery by holding down power button and volume up. That will get you into cwm. From there, wipe data, cache, dalvik, and flash rom. Reboot, enjoy
Sent from my SPH-D710BST using xda premium
Click to expand...
Click to collapse
Thanks that got me into cwm but for some reason the power button will not let me choose any options. Not sure if it is lagging or being unresponsive. The volume up and down buttons at least work.

Cabhills said:
Thanks that got me into cwm but for some reason the power button will not let me choose any options. Not sure if it is lagging or being unresponsive. The volume up and down buttons at least work.
Click to expand...
Click to collapse
Lol, that's because the select button is home button by default. Press up down up on volume to enable power button
Sent from my SPH-D710BST using xda premium

jdsingle76 said:
Lol, that's because the select button is home button by default. Press up down up on volume to enable power button
Sent from my SPH-D710BST using xda premium
Click to expand...
Click to collapse
I have done that but the power button still does not allowed me to select any of the options after using the volume up and down buttons to choose one.

Cabhills said:
I have done that but the power button still does not allowed me to select any of the options after using the volume up and down buttons to choose one.
Click to expand...
Click to collapse
Reboot into recovery again....at the first screen, press volume up, down, then up again, it will activate the power button. Or stay where you are and use the home key(does the same thing as power button)
Sent from my SPH-D710BST using xda premium

So now for some odd reason the power button is working now..... Quick question: I did not load tdunham's rom onto my phone yet. If I can not get past the boot screen after wiping the cache/dalvik what should I do then? Re-install the stock GB27 rom to get the old kernel back? I'm assuming the wipe data will do a factory reset so that would re-install the old kernel itself?

jdsingle76 said:
Reboot into recovery again....at the first screen, press volume up, down, then up again, it will activate the power button. Or stay where you are and use the home key(does the same thing as power button)
Sent from my SPH-D710BST using xda premium
Click to expand...
Click to collapse
That explains that -_-. It has been a year since I flashed anything which you can already tell...... I try not to use odin if I can since I've used cwm to flash all my modems and roms. Also this five min waiting between post is why this post will be a bit late.

Cabhills said:
So now for some odd reason the power button is working now..... Quick question: I did not load tdunham's rom onto my phone yet. If I can not get past the boot screen after wiping the cache/dalvik what should I do then? Re-install the stock GB27 rom to get the old kernel back? I'm assuming the wipe data will do a factory reset so that would re-install the old kernel itself?
Click to expand...
Click to collapse
Td's rom has cwm. If you get bootloop, reboot into recovery wipe everything, and try again. Still getting boot loop, probably bad download. Dl again using computer instead of phone then save to phone before flashing again
Sent from my SPH-D710BST using xda premium

jdsingle76 said:
Td's rom has cwm. If you get bootloop, reboot into recovery wipe everything, and try again. Still getting boot loop, probably bad download. Dl again using computer instead of phone then save to phone before flashing again
Sent from my SPH-D710BST using xda premium
Click to expand...
Click to collapse
Did a data wipe and still have a bootloop with the yellow triangle at the bottom. I'm guessing it is the el26 kernel that is causing it. This is from his OP page:
3. Install EL26 (Chris41G) kernel or EL29 Directboot kernel.
They can be found here: http://forum.xda-developers.com/show....php?t=1662295
( Look for: GB - Stock EL26 Repacked Kernel or GB - Direct Boot CWM )
Note: For success, EL26 & EL29 kernels are recommended for flashing this rom!
I used the EL26 one and it seems to not to be working with the stock GB27 rom (At least through the odin method). I've read that Stock rooted JB kernels for some reason do not play nice with custom JB roms. Am I able to get into Odin mode safely from the boot screen and can I just used the one-click Stock GB27 again to reinstall everything back to stock?

Cabhills said:
Did a data wipe and still have a bootloop with the yellow triangle at the bottom. I'm guessing it is the el26 kernel that is causing it. This is from his OP page:
3. Install EL26 (Chris41G) kernel or EL29 Directboot kernel.
They can be found here: http://forum.xda-developers.com/show....php?t=1662295
( Look for: GB - Stock EL26 Repacked Kernel or GB - Direct Boot CWM )
Note: For success, EL26 & EL29 kernels are recommended for flashing this rom!
I used the EL26 one and it seems to not to be working with the stock GB27 rom (At least through the odin method). I've read that Stock rooted JB for some reason do not play nice with custom JB roms. Am I able to get into Odin mode safely from the boot screen and can I just used the one-click Stock GB27 again to reinstall everything back to stock?
Click to expand...
Click to collapse
Sure you can, and it sounds like a bad download. His Rom is solid. Try downloading it, and matching md5, and its not the el26 either. It's a work horse for flashing, and solid as the day is long. Sounds like bad dl. Don't give up
Sent from my SPH-D710BST using xda premium

jdsingle76 said:
Sure you can, and it sounds like a bad download. His Rom is solid. Try downloading it, and matching md5, and its not the el26 either. It's a work horse for flashing, and solid as the day is long. Sounds like bad dl. Don't give up
Sent from my SPH-D710BST using xda premium
Click to expand...
Click to collapse
I have his rom downloaded but I have not flashed it yet. When I meant stock GB27 I meant this: [ROM][ODIN][TAR]SPH-D710 GB27 (GB27 Modem/Kernel/ROM - Root/Stock) from http://www.sxtpdevelopers.com/showthread.php?t=166. That is the one I wanted to re-flash in odin to see if it will let me reboot back but I do not know if re-flashing with a yellow triangle will screw things up. I have not clue why I needed to flash a EL26/EL29 kernel to flash his rom though which is how this all started.

Well I re-flashed the Stock GB27 again and everything work with the yellow triangle gone. I guess I have to put custom rom and Jellybean X2 Format utility on my phone before I flash the kernel. Just sucks the counter is going to go up cause of odin -_-. Welp lets try this again. Thank you for all your help jdsingle76.

Cabhills said:
Well I re-flashed the Stock GB27 again and everything work with the yellow triangle gone. I guess I have to put custom rom and Jellybean X2 Format utility on my phone before I flash the kernel. Just sucks the counter is going to go up cause of odin -_-. Welp lets try this again. Thank you for all your help jdsingle76.
Click to expand...
Click to collapse
Don't worry about the counter. Triangle Away after you're settled . And you're very welcome. Glad I could help.
Sent from my SPH-D710BST using xda premium

Instead of using PC Odin. You can grab Mobile Odin lite 3.65 by chainfire and flash the
DirectBoot EL29 Recovery Kernel.
You mentioned you don't know why you need the
EL26/29 Kernel recovery. It's a safe recovery
to flash roms and recommended to do so.

Use PC odin, the directions provided are a stable sure fire way to fix the problem. If you're going to go the Mobile Odin route, get the pro version. The lite version requires you to find and download an extra file, which can complicate things if you're unsure, and flashing the wrong one WILL cause a brick.
Trust the more experienced users here and it will save you time, trouble, and possibly a device:good: