Develop Bugs

[Q] Possible brick? Any ideas?

Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!

munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?

assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium

barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.

barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...

http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium

munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.

playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(

munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse

barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.

Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5

munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.

barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.

munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.

barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5

ET4G and brickbug app (How many bricks are there really over here)

So I am on my fourth ICS rom and haven't had any problems with a brick. I jumped on xda a today ans daw this http://www.xda-developers.com/android/determine-your-devices-hard-brick-risk-with-got-brickbug/
Now I download the app and it told me this
{
"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"
}
Now is this due to a brick bug or just people doing something stupid?

As long as you follow OP directions and flash from el26 cwm kernel, you will be OK.
Sent from my SPH-D710 using Tapatalk

I'm staying away until ics is an official release, but that's just me being safe than sorry.

I see you flashed Venums latest rom. I tried it out last night but just wasn't feeling it. Any time you flash anything there is a chance of a brick. Keep that in mind and you will be fine. Do your homework check the md5 then flash. If you are not sure then don't flash and remember qbking77 probably has a youtube video already so watch it.

someguyatx said:
I see you flashed Venums latest rom. I tried it out last night but just wasn't feeling it. Any time you flash anything there is a chance of a brick. Keep that in mind and you will be fine. Do your homework check the md5 then flash. If you are not sure then don't flash and remember qbking77 probably has a youtube video already so watch it.
Click to expand...
Click to collapse
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2

oscarthegrouch said:
I'm staying away until ics is an official release, but that's just me being safe than sorry.
Click to expand...
Click to collapse
I will tell you something about Samsung and there official releases. When I had my cappy they keep saying there will be an update for froyo and before you know it I was flashing GB and still no release. Lol
Sent from my SPH-D710 using Tapatalk 2

dfuse06 said:
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I am glad your laughing. I guess when Google engineers ran into the bug they were doing something stupid? I guess when they had Samsung write new firmware for eMMC chips going into the GNex it was because they were doing something stupid. I guess when all the Kernel and recovery developers bricked their phones and they couldn't even be jtag'd they were doing something stupid. Actually technically when you develop you know their are risks, but this risk is not something anyone expected. It is a permenant bug that will always be with your phone, things will be done to avoid it. But the danger isn't going away. Even after the OTA, as we are finding out there is still the danger of the calls being made from CWM zips, etc.
Just keep hitting factory reset in ICS, quickest way to do it and it still may take a few tries. If you think its perfectly okay that the Galaxy Note was push an update that causes random bricks when people factory reset thats fine. But you can't tell them they were doing something stupid when Samsung never emailed them to say "Don't factory reset".
Its a hard cold fact that sooner or later one of the times mmc_erase() is called with the flag MMC_CAP_ERASE corruption will occur at the wearlevelfs level which can only be fixed by vendor specific commands not available to even repair centers.
4 roms? I did a few the wrong way. But 4 roms altogether? Many of us are around 30 and thats unique not reflashes. Probably around 200 total flashes myself just for ICS on this device. I am home on CM9 now which means only a couple a week from now on i think.

RainMotorsports said:
I am glad your laughing. I guess when Google engineers ran into the bug they were doing something stupid? I guess when they had Samsung write new firmware for eMMC chips going into the GNex it was because they were doing something stupid. I guess when all the Kernel and recovery developers bricked their phones and they couldn't even be jtag'd they were doing something stupid. Actually technically when you develop you know their are risks, but this risk is not something anyone expected. It is a permenant bug that will always be with your phone, things will be done to avoid it. But the danger isn't going away. Even after the OTA, as we are finding out there is still the danger of the calls being made from CWM zips, etc.
Just keep hitting factory reset in ICS, quickest way to do it and it still may take a few tries. If you think its perfectly okay that the Galaxy Note was push an update that causes random bricks when people factory reset thats fine. But you can't tell them they were doing something stupid when Samsung never emailed them to say "Don't factory reset".
Its a hard cold fact that sooner or later one of the times mmc_erase() is called with the flag MMC_CAP_ERASE corruption will occur at the wearlevelfs level which can only be fixed by vendor specific commands not available to even repair centers.
4 roms? I did a few the wrong way. But 4 roms altogether? Many of us are around 30 and thats unique not reflashes. Probably around 200 total flashes myself just for ICS on this device. I am home on CM9 now which means only a couple a week from now on i think.
Click to expand...
Click to collapse
I hear you dude.I am just saying if this is a known bug and ppl are still flashing ROMs with high risk of bricking. That is stupid. Not everyone has the money to get another phone if they brick. But it is the way the game goes. Thanks for the info I didnt know it was really all that bad. Looks like I will be going back ti el26 everytime I flash.
Edit and that still sucks,and this only ics? is GB safe?
Sent from my SPH-D710 using Tapatalk 2

Even though the app reports bricking probabilities, you shouldn't assume any firmware rev is safe. Per the EMMC lockup discussion thread, fwrev 0x25 (which brickbug reports as "probably safe") has a separate data corruption issue. Until there's a definite solution, if you're flashing ICS ROMs, you should follow the forum instructions and flash back down to EL26 w/ CWM and then back up or you're risking a brick.
EDIT: Flashing to an ICS ROM from EL26 w/ CWM is as safe as any regular flashing operation though, and speaking as someone that dragged their feet to flash up to ICS - it's worth taking the leap now if you're okay with a couple of hiccups (Blu Kuban here). Incredible experience and fairly easy to go back and forth if you take nandroid and titanium backups.

One again thanks to all for all the info. I had some phones that I tought were just unbrick able. I use to try everything on my cappy and the jig what the bomb. lol
Sent from my SPH-D710 using Tapatalk 2

dfuse06 said:
I hear you dude.I am just saying if this is a known bug and ppl are still flashing ROMs with high risk of bricking. That is stupid. Not everyone has the money to get another phone if they brick. But it is the way the game goes. Thanks for the info I didnt know it was really all that bad. Looks like I will be going back ti el26 everytime I flash.
Edit and that still sucks,and this only ics? is GB safe?
Click to expand...
Click to collapse
Was talking to Chris41G last night he detailed some of the paths that were likely to brick still. SFHUB has been working on ways for developers to make their Recoveries and CWM Zips safe. Even with recoveries that are safe to wipe with some zips can still trigger the bug.
As far as GB goes, Calk's format all has a known safe updater binary. The cap erase flasg was not enabled on our GB kernel but as was also found out is still apparently safe if enabled. I cant remember what command it is but on ICS something like makeext4fs() is now called and is part of the problem. But only code compiled against the library that uses that even calls it.
We were all messing with leaks and its all our fault if something happens. We all have instructions and if someone doesn't read or follow them then yeah that is stupid. However the Galaxy Note was pushed ICS OTA without a workaround (which the GS2 i9100 has) and people were able to brick by just factory resetting which seems to be one of the easiest ways.
Googles engineer Ken Sumrall said the area for the /Data partition being the one to go was because it was written to more often, more chances. This thread - http://forum.xda-developers.com/showthread.php?t=1644364 has more information than I can even explain but may also be a hard read. They found the problem with the eMMC firmware while developing the Gnex, the prototypes had the same eMMC firmware as our phone. This can be update at the factory but not by the end user. The corruption occurs at a lower level than is presented as writable storage and can not be fixed by JTAGing firmware. It is possible for some super bricks to be partitioned around, others not.
ODIN is safe too by the way so if your ODINing your leaks no real worries there, there was some question as to calls made by Mobile ODIN which i flashed the EL26 kernel probably 25+ times with.

RainMotorsports said:
Was talking to Chris41G last night he detailed some of the paths that were likely to brick still. SFHUB has been working on ways for developers to make their Recoveries and CWM Zips safe. Even with recoveries that are safe to wipe with some zips can still trigger the bug.
As far as GB goes, Calk's format all has a known safe updater binary. The cap erase flasg was not enabled on our GB kernel but as was also found out is still apparently safe if enabled. I cant remember what command it is but on ICS something like makeext4fs() is now called and is part of the problem. But only code compiled against the library that uses that even calls it.
We were all messing with leaks and its all our fault if something happens. We all have instructions and if someone doesn't read or follow them then yeah that is stupid. However the Galaxy Note was pushed ICS OTA without a workaround (which the GS2 i9100 has) and people were able to brick by just factory resetting which seems to be one of the easiest ways.
Googles engineer Ken Sumrall said the area for the /Data partition being the one to go was because it was written to more often, more chances. This thread - http://forum.xda-developers.com/showthread.php?t=1644364 has more information than I can even explain but may also be a hard read. They found the problem with the eMMC firmware while developing the Gnex, the prototypes had the same eMMC firmware as our phone. This can be update at the factory but not by the end user. The corruption occurs at a lower level than is presented as writable storage and can not be fixed by JTAGing firmware. It is possible for some super bricks to be partitioned around, others not.
ODIN is safe too by the way so if your ODINing your leaks no real worries there, there was some question as to calls made by Mobile ODIN which i flashed the EL26 kernel probably 25+ times with.
Click to expand...
Click to collapse
Yeah i just bought moble odin pro
Sent from my SPH-D710 using Tapatalk 2

dfuse06 said:
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either

manufan721 said:
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
Click to expand...
Click to collapse
[/url][/IMG]

manufan721 said:
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
Click to expand...
Click to collapse
well dude this comment was not at you and when I said something stupid I mean stupid I had a cappy has my 1st android phone and I flashed rom from other phone and just doing stupid stuff,but we had home made jigs that unbrick anything. It didn't matter, plus a dev should test a non stable rom them self. Any mod, theme, I mean anything I post I test myself to ensure nothing well happen to anyone's phone.Sorry if I got you panties in a bunch'but come on dude read every post you took this the wrong way'but yeah no hard feeling man. Good luck to you, and not bricking your phone again.

rwright64 said:
[/url][/IMG]
Click to expand...
Click to collapse
Lmfao
Sent from my SPH-D710 using Tapatalk 2

dfuse06 said:
well dude this comment was not at you and when I said something stupid I mean stupid I had a cappy has my 1st android phone and I flashed rom from other phone and just doing stupid stuff,but we had home made jigs that unbrick anything. It didn't matter, plus a dev should test a non stable rom them self. Any mod, theme, I mean anything I post I test myself to ensure nothing well happen to anyone's phone.Sorry if I got you panties in a bunch'but come on dude read every post you took this the wrong way'but yeah no hard feeling man. Good luck to you, and not bricking your phone again.
Click to expand...
Click to collapse
Good answer bro..no hard feelings on my end either.. if i did take this the wrong way then i apologize for it..

Download mode - Odin will only recognize when phone is booted up

I am at my wits end right now. I can see my phone on com3 when it is booted up all the way, but it will not see it when in download mode. I erroneously flashed this file earlier, forgetting I did not have a regular GSII: I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar.md5
What other information would help diagnose this problem?
I currently have stock EL26 installed.
Alternatively, is it safe to install CM9 from this recovery? Seems to me I should resolve this first..
edit: I do not have an unrecognized device, I have tried more than one usb cable and port

Try this:
Redownload the drivers for the phone, install them and let your cpu reset. See if Odin sees your phone then.
I know with my GT10.1 it takes a few seconds more for Odin to see it so... But my ET4G pops up pretty fast.
The EL26/CWM is the kernel/recovery that you want to use when your flashing CM9 Alfa 5 and below.
But like you said... You may want to figure out why Odin isn't seeing your phone when it's in download mode.
Also... Do you have Kies installed on your cpu??? It'll cause problems with Odin to.
Have you tried Mobile Odin for what you want to do. I do almost everything involving CM and flashing with it. Works like a charm.
Sent From My Galaxy Class Star Fighter...

How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium

fryingpan0613 said:
How in the hell do you forget you don't have a international version?! Smh
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
WoW... He just edited his post as I was replying... Doesn't flashing an international tar mess up the bootloader??? I'm really not to sure where you go next.
If his phone still boots up okay couldn't help still use Mobile Odin and flash the right setup.
What was that old school Saturday morning psa... "Reading is fundamental" or something like that.
Sent From My Galaxy Class Star Fighter...

What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.

hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Edit: driver reinstall did not work, do not have kies installed. mobile odin works on GB then? I can use the e4gt-autofix if that makes a difference. Updating from the stock recovery does not seem to work, it will start, then give me the ! triangle with sad android.
Click to expand...
Click to collapse
Unfortunately my friend, I think you are hosed. The international PIT file is exceptionally different from the one we use for our phone. I don't remember the specifics but basically it remaps your partitions and causes USB to not work correctly. Your best bet is to try a JTAG service. I've heard MobileTechVideos.com is pretty well rated.
Sorry!

My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Edit: ok I take it back, mass storage is not working either. also, I am definitely willing to buy Mobile Odin if anyone has any ideas.

hilo4321 said:
What is the right setup to use? A fresh GB rom install? I am at a loss at this point.
Yeah I ****ed up, I have not messed with my phone in many months.
Click to expand...
Click to collapse
Not getting on you m8 but... Flashing a rom for another device even if it's the same model is really really bad. Like rwilco said, yes the International GS2 and our ET4G's are the same devices but there software is very different.
hilo4321 said:
My phone is currently functioning properly when booted up. What are the implications of this beyond not being able to change roms (and not having a notification bar..wtf)?
Click to expand...
Click to collapse
Well... Like you said, most likely you will not be able to make any changes as in roms, kernels or things like that. And if you have any hardware issue you won't be able to get any support from Sprint. And you sure as hell won't be able to receive any OTA's from Sprint or Samsung.
Can you do something for use... Go to "Settings" then "About Phone" and under "Model Number" & "Baseband Version" and tell us what it says there.
I'm not really sure this would/can help you but if your phone still boots and runs you maybe able to Odin the right tar file and see if that fixes it. I mean it could work but I really doubt it. And what's the worst that could happen... It could brick it, then you could file an insurance claim... Just saying...
Where did you get the file from that you flashed??? Most likely not from this (ET4G) forum, should have read up a bit more before you started messing around with flashing roms again. Some things aren't easily fixable.
Sent From My Galaxy10.1 Class Starship....

I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
My baseband is S710.10 S.EK02 with standard model number sph d710.
I believe it came from the android forums, but like i said it was in the SGII area.
What tar file would I be looking for?

Doing some research m8... Give me a few mins....
Make sure you have Mobile Odin installed.
Sent From My Galaxy Class Star Fighter...

hilo4321 said:
I am a lucky SOB. I was able to use e4gtauto-sfx to put el29/CWM back on to my phone, and as a result I restored my nandroid backup. I have full function back, except, of course, no odin in download mode.
Click to expand...
Click to collapse
Ok... Yes you are my friend!!!! But I fear we are not completely out of the woods as of yet. You still have the "no Odin in download" thing still. And that could still be an issue, but at least your back up and running.
hilo4321 said:
My baseband is S710.10 S.EK02 with standard model number sph d710.
Click to expand...
Click to collapse
This is telling me that your on an older baseband... I'm running CM9 and my baseband reads "EL29" which I think is the most resent/updated baseband. I don't want to scare you but I really wish a dev would jump in here and shed some of there wisdom. (I'm almost to the point where I'm winging it.) But I feel we need to get your baseband to EL29.
hilo4321 said:
I believe it came from the android forums, but like i said it was in the SGII area.
Click to expand...
Click to collapse
From now on promise us you'll just use this site and forum for all of your download needs.... Please.
hilo4321 said:
What tar file would I be looking for?
Click to expand...
Click to collapse
Try this post... http://forum.xda-developers.com/showthread.php?t=1433101
Follow the instructions for the Android Install, about halfway down in the first post.
Sent From My Galaxy10.1 Class Starship....

Oh sweet Jesus, I promise.
Now when I do this will this wipe everything? I'm not terribly clear on that. Seems to me that it will.
I really appreciate the help man.

There are 2 different versions... One will wipe everything and one will leave all of your user data intact.
And like I said, I'm not a 100% sure this will fix it but I think we are moving in the right direction.
And not a problem... It's helping me learn more about what goes on inside our devices.
I am still a little worried about your bootloader though. If that was jacked up by flashing the wrong rom I don't know if this will fix it.
Question, when you hook up your device to your cpu when it's booted up are you still able to do things like transfer files and such???
Sent From My Galaxy10.1 Class Starship....

I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.

hilo4321 said:
I can use mass USB now. I wont be able to test the el29 now though as I'm away now. I will report back when I can.
Click to expand...
Click to collapse
That's great brother.... I'm really glad I could help ya get up and running to the point where you can a least have a use able device.
Sent From My Galaxy10.1 Class Starship....

EL29 was the last version of Gingerbread put out. You'll be able to use mobile Odin to flash stuff but you'll never get the USB to recognize in DL mode. I think jtag might be the only way to restore complete functionality.
---------- Post added at 11:42 PM ---------- Previous post was at 11:36 PM ----------
For now you'll be alright as long as you can get into recovery mode fine then you can flash modems in there(since mobile Odin can't flash them for our phone).

Your baseband (modem) should not matter and changing it won't have any affect on your problem. Good luck and let us know how out turns out.

Solved
I am posting now in case someone comes upon this post down the road.
I am now running cyanogen 9 on my e4gt. This thread saved me, as I was finally able to get odin to work. With that, I was able to flash a new recovery onto my phone (I used StockCWM-EL26). Then once I got that on there I flashed over to the Beta 1 build of Cyanogenmod for e4gt.
I'm sorry I can't be more clear or provide links, it took me a lot of crawling around the forums to figure this out. Perhaps someone more knowledgeable than I can clean up/expand my post. Let me tell you though, it feels really good to get this thing running smoothly again.
If you have any questions I'll try to help.
Good luck, idiot!

That's awesome dude. Remember stay in this forum :beer::thumbup:
sent from MY BAD A$$ ET4G

Note 2 stuck on Samsung Logo

Couldnt find threads related to my specific device so i made it.
After installing a custom rom on my tmobile gn2 (hyperdroid pegasus) i realized that my SIM card wasnt being detected. Having run into this problem before i decided to use the gn2 toolkit to re-flash a stock rom and start from scratch, which worked and allowed my sim card to be detected use my mobile network (TMOBILE USA)
Only after installing hyperdroid and trying to reflash the stock rom, the custom hyperdroid rom would stay on the device after multiple attempts! Being clever, i decided to download and reflash the rom using ODIN only in download mode which worked and now the device is running the Samsung Official build branded with tmobile but will not boot past the samsung logo (one of two that i see appear upon boot)
Looking at a thread for the original Note 1, do i assume correctly that my phone is now bricked? If so, anyone else know of an absolute md5/tar image i can use that can get me back to factory out of the box, i bought this phone unsubsidized over the iphone5 because i wanted something that woulc pack a wallop. Now im just walloping myself for wasting not just 100 dollars more but 750 dollars on a device, running an os, being supported by everyone who wants their hands on it, in a community that will chew you out if you ask incorrectly.
So im whining yes but i could use some advice. Sure im a noob but so were you once, all i reall ask for is some compassion. thanks...

Did you try factory reset?
Sent from my SGH-T889 using xda premium

Try to use odin root66 for prerooted or stock
After odin do factory reset
Sent from my SGH-T889 using xda premium

Thanks for replies, really appreciated
I cannot begin to explain this ordeal i had with my note 2. Thanks for the replies as of this point however, actually directions that i took in figuring it all out and getting my phone back to factory defaults...
So to elaborate, my N2 has been rooted for a few days and i decided to install a custom ROM, which disabled or didn't support my SIM. Trying to undo the flash and go back to a ROM i was using via ROM manager, i realized it could not be undone. Every time i tired to reflash a(ny) zip from my device using rom manager i was still booting with the custom malfunctioning rom (Hyperdroid Pegasus)
After realizing that i couldn't undo the flash of the custom rom via ROM manager, the galaxy note 2 toolkit or via ODIN straight up, i somehow ended up bricking my phone using an image i got off of samsung-updates (which i downloaded using the galaxy n2 toolkit). In bricking i mean it would power on and boot into the samsung whirlpool, then the tmobile 4g accelerated android, and then to a glowing samsung logo and didn't progress from there.
Doing some research i noticed that there was a more recent image version for my specific device (jan 5 2013) downloaded it and gave that a try, flashed it via ODIN (because by the time it was bricked Download mode / Odin mode and ODIN 3.07 for windows was my only available option!) and launched up my gn2... ONLY to find it booting to the animations and then looping them! WTF?!
So more research and i got to a recovery mode, wiped my data and finally voila. (Even samsung support couldn't support this...)
No discredit to the Hyperdroid Rom, I'm sure it works for a lot of people out there but i guess it doesn't like my tmobile note 2 sgh-t889.
I just hoped if anyone else ran into the same problem, download the image from samsung-updates.com, the latest of course! Then, (if you can boot into download mode that is) use ODIN (i used version 3.07) to load the image you got off samsung-updates (OSM will take more or less 5 minutes to check the md5 package so don't panic)
If your lucky you shouldn't have to do anything else, but if you get into a weird situation when you can't get past the boot animation screens, boot into recovery mode (which i THINK is hold down UP, POWER, AND THE HOME KEY as it powers up) and select to CLEAR WIPE DATA or FACTORY RESET.
Hopefully after wiping you should have successfully re-flashed a "bricked" galaxy note 2 that won't boot past the animation screens.
Thanks for reading! Im here to answer any questions or help, maybe i won't play with custom rome anymore but id sure like to start building my own!

Rhiannon224 said:
Did you try factory reset?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
jay661972 said:
Try to use odin root66 for prerooted or stock
After odin do factory reset
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
To both you guys, i just want to say i elaborated on your answers for the benefit of helping someone like me who craves detail. No offense to you guys, but i was racketing with Samsung about this and driving their people nuts! the solution had came to me before i saw your replies so I'm just glad i took the right path in it all and i guess i admit i lost faith in XDA for a second there. anyways :good:

So wait, in all that flashing and reflashing and messing with Odin, you hadn't done a factory reset yet? Isn't that the first step almost any ROM dev(or even any normal flashoholic on these forums) will tell you to take?

shinkinrui said:
So wait, in all that flashing and reflashing and messing with Odin, you hadn't done a factory reset yet? Isn't that the first step almost any ROM dev(or even any normal flashoholic on these forums) will tell you to take?
Click to expand...
Click to collapse
I give you permission to call me a newb, Okay? Feel better and call me in the morning.

Lol no need to get offended man It's a learning experience.
I only said something because you seemed so bitter about your perceived lack of support around here and even went so far as to say you almost lost faith in xda, yet it seems like you didn't do step 1.
At any rate, glad your note 2 is revived
Sent from my SGH-T989 using xda app-developers app

2ruen0 said:
I give you permission to call me a newb, Okay? Feel better and call me in the morning.
Click to expand...
Click to collapse
This seemed fitting...
{
"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"
}
Still, good on you for learning a few things and getting your phone back in action.

shinkinrui said:
Lol no need to get offended man It's a learning experience.
I only said something because you seemed so bitter about your perceived lack of support around here and even went so far as to say you almost lost faith in xda, yet it seems like you didn't do step 1.
At any rate, glad your note 2 is revived
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Darkshado said:
This seemed fitting...
Still, good on you for learning a few things and getting your phone back in action.
Click to expand...
Click to collapse
Lol, funny picture. Yes i almost lost faith but obviously you guys came through. I am one of 4 million people who did or didnt follow the rules but thats a good thing, i think the tmobile jellybean community needs as much help as it can get right now and if it takes making a tiny mistake good for us.
actually shinkinrui, i wasnt sure if you were trying to troll me or trying to remind me that this forum is for the leet and the leet only. I understand the work devs go through, but its still a community that needs to thrive, not be put off or put down.

Neither, actually. I was annoyed at the implication that it was this community's fault you went through your ordeal. Like someone blaming their cable company for their cable not working when they just didn't change the input on their TV.
And my post didn't insult you, it pointed out your mistake. Big difference

Thanks !!!
2ruen0 said:
I cannot begin to explain this ordeal i had with my note 2. Thanks for the replies as of this point however, actually directions that i took in figuring it all out and getting my phone back to factory defaults...
So to elaborate, my N2 has been rooted for a few days and i decided to install a custom ROM, which disabled or didn't support my SIM. Trying to undo the flash and go back to a ROM i was using via ROM manager, i realized it could not be undone. Every time i tired to reflash a(ny) zip from my device using rom manager i was still booting with the custom malfunctioning rom (Hyperdroid Pegasus)
After realizing that i couldn't undo the flash of the custom rom via ROM manager, the galaxy note 2 toolkit or via ODIN straight up, i somehow ended up bricking my phone using an image i got off of samsung-updates (which i downloaded using the galaxy n2 toolkit). In bricking i mean it would power on and boot into the samsung whirlpool, then the tmobile 4g accelerated android, and then to a glowing samsung logo and didn't progress from there.
Doing some research i noticed that there was a more recent image version for my specific device (jan 5 2013) downloaded it and gave that a try, flashed it via ODIN (because by the time it was bricked Download mode / Odin mode and ODIN 3.07 for windows was my only available option!) and launched up my gn2... ONLY to find it booting to the animations and then looping them! WTF?!
So more research and i got to a recovery mode, wiped my data and finally voila. (Even samsung support couldn't support this...)
No discredit to the Hyperdroid Rom, I'm sure it works for a lot of people out there but i guess it doesn't like my tmobile note 2 sgh-t889.
I just hoped if anyone else ran into the same problem, download the image from samsung-updates.com, the latest of course! Then, (if you can boot into download mode that is) use ODIN (i used version 3.07) to load the image you got off samsung-updates (OSM will take more or less 5 minutes to check the md5 package so don't panic)
If your lucky you shouldn't have to do anything else, but if you get into a weird situation when you can't get past the boot animation screens, boot into recovery mode (which i THINK is hold down UP, POWER, AND THE HOME KEY as it powers up) and select to CLEAR WIPE DATA or FACTORY RESET.
Hopefully after wiping you should have successfully re-flashed a "bricked" galaxy note 2 that won't boot past the animation screens.
Thanks for reading! Im here to answer any questions or help, maybe i won't play with custom rome anymore but id sure like to start building my own!
Click to expand...
Click to collapse
Thamks !!!! alot man this post help me:highfive:

"wiping data / factory install" selection worked for me
Thanks for this tip!
I was stuck on the Samsung animation logo after flashing to 4.1.1 so that I could unlock my phone. :crying:
I went to the recovery mode and hit the "wipe data / factory install" selection and it rebooted into the 4.1.1 ROM successfully.
Awesome! :laugh:

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] Note 3 stuck at the logo screen

I'm a new member, just made this acc a minute ago, forgive me if i did anything wrong, i'll read the rules later.
anyways...
I rooted my device when i got this phone, use it with Odin, and earlier this morning, i tried to unroot it, 'cause i want to update the phone, since it says that i modified my phone and blah blah.. so i unroot my phone using supersu, and restart the phone, but i still can't update the phone, so i give up and i tried to root the phone again
what i did was:
1) i connect my phone, open PDA
2) next, i'm not really sure which file i was supposed to open, so i click random file .-. most likely the third or second one, i'll show you how it look 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"
}
and that's when it started to go wrong.. when i tried to turn it back off and on again, it stuck at the logo screen where it says samsung note 3, it just stuck there.
next i tried to root the phone again, i thought if i did it again correctly, it might work, so i open the pda file again and clicked CF-auto root file (most likely)
it still doesnt work..
then i tried to press the power button + up + home, it doesnt work, it showed the android thing and then get back straight on the logo screen again, and it just stuck there.
i tried again over and over, i even pulled out the battery, but it doesnt work.
i wonder if i should go to t-mobile and had them repair it, but i doubt they will, since they would know i rooted my phone, and besides i dont even know if i have the warranty or not.
please someone help me, thank you very much!!!

Note 3 stuck at the logo screen
midomi333 said:
I'm a new member, just made this acc a minute ago, forgive me if i did anything wrong, i'll read the rules later.
anyways...
I rooted my device when i got this phone, use it with Odin, and earlier this morning, i tried to unroot it, 'cause i want to update the phone, since it says that i modified my phone and blah blah.. so i unroot my phone using supersu, and restart the phone, but i still can't update the phone, so i give up and i tried to root the phone again
what i did was:
1) i connect my phone, open PDA
2) next, i'm not really sure which file i was supposed to open, so i click random file .-. most likely the third or second one, i'll show you how it look like
and that's when it started to go wrong.. when i tried to turn it back off and on again, it stuck at the logo screen where it says samsung note 3, it just stuck there.
next i tried to root the phone again, i thought if i did it again correctly, it might work, so i open the pda file again and clicked CF-auto root file (most likely)
it still doesnt work..
then i tried to press the power button + up + home, it doesnt work, it showed the android thing and then get back straight on the logo screen again, and it just stuck there.
i tried again over and over, i even pulled out the battery, but it doesnt work.
i wonder if i should go to t-mobile and had them repair it, but i doubt they will, since they would know i rooted my phone, and besides i dont even know if i have the warranty or not.
please someone help me, thank you very much!!!
Click to expand...
Click to collapse
--update-- 4:36 pm
when i tried to charge the phone, theres this loading sign but, the green things wont show up, you know how you charge your phone and then theres this green thing that shows up . or has it always been that way?
the screen wont turn off too, it usally does.

First off welcome.. 2nd. What update . There is not a tmobile update.
3rd.. You need to know what your doing with Odin. You can muff your phone up if you dont know..
That being said read this. ... http://forum.xda-developers.com/showthread.php?p=46084013 read thru it 2 or 3 times and do exactly what I wrote
Sent from my SM-N9005
Sent from my SM-N9005 using Tapatalk

deeznutz1977 said:
First off welcome.. 2nd. What update . There is not a tmobile update.
3rd.. You need to know what your doing with Odin. You can muff your phone up if you dont know..
That being said read this. ... http://forum.xda-developers.com/showthread.php?p=46084013 read thru it 2 or 3 times and do exactly what I wrote
Sent from my SM-N9005
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
whenever i reboot my phone they told me to update, but since i root my phone, i cant do that. they said something about my device being modified. yes i know, sorry about that, i was being stupid, i shouldve read the instructions again.
that being said, why should i tried to root the phone again? i doubt that trying to root the device again will solve the problem, since when i did that last time, it passed, but the device wont start and i stuck at the samsung logo. i bet something like that will happen again. soo... is there a reason why you think it will work?
btw thanks for replying.

midomi333 said:
whenever i reboot my phone they told me to update, but since i root my phone, i cant do that. they said something about my device being modified. yes i know, sorry about that, i was being stupid, i shouldve read the instructions again.
that being said, why should i tried to root the phone again? i doubt that trying to root the device again will solve the problem, since when i did that last time, it passed, but the device wont start and i stuck at the samsung logo. i bet something like that will happen again. soo... is there a reason why you think it will work?
btw thanks for replying.
Click to expand...
Click to collapse
Your not stupid m8 don't bash yourself. Every single Member here was new once. We all make mistakes and ask for Help. Its ok. But you should of done some reading bud I dont like odin myself but had to use it to root my note3 and note2 but always read and read because if you stop for a moment think about it. 700$ device can become worthless in just a click.
Sent from my SM-N900T using Tapatalk

midomi333 said:
whenever i reboot my phone they told me to update, but since i root my phone, i cant do that. they said something about my device being modified. yes i know, sorry about that, i was being stupid, i shouldve read the instructions again.
that being said, why should i tried to root the phone again? i doubt that trying to root the device again will solve the problem, since when i did that last time, it passed, but the device wont start and i stuck at the samsung logo. i bet something like that will happen again. soo... is there a reason why you think it will work?
btw thanks for replying.
Click to expand...
Click to collapse
The thread I linked isnt rooted its stock just like the first time you turned it on
Trust me the things you showed that you could have flashed wouldn't kill your phone. Just do what the linked thread says. If it still won't boot let me know ( here or in pm) . Btw I wasn't trying to bash. ☺??
Sent from my SM-N9005 using Tapatalk
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
chuko303 said:
Your not stupid m8 don't bash yourself. Every single Member here was new once. We all make mistakes and ask for Help. Its ok. But you should of done some reading bud I dont like odin myself but had to use it to root my note3 and note2 but always read and read because if you stop for a moment think about it. 700$ device can become worthless in just a click.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Believe it or not using odin is one of the best things about having a Samsung phone. ...
Sent from my SM-N9005 using Tapatalk

deeznutz1977 said:
The thread I linked isnt rooted its stock just like the first time you turned it on
Trust me the things you showed that you could have flashed wouldn't kill your phone. Just do what the linked thread says. If it still won't boot let me know ( here or in pm) . Btw I wasn't trying to bash. ☺??
Sent from my SM-N9005 using Tapatalk
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
Believe it or not using odin is one of the best things about having a Samsung phone. ...
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
thank you!! it worked!! but my device still hast been rooted yet, i wonder if i should root it ? .. but i dont want the same thing to happen twice TT TT . oh i think the problem happen because of my original usb, it doesnt fit perfectly to my phone, so sometimes it got disconnected quiet a lot, unless i hold it.. i wonder if it got disconnected while i try to root the phone? anyways, thank you very much.