Develop Bugs

ClockworkMod Recovery for Galaxy S (BETA BEWARE)

WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.
At the time of this writing only a single working flash has been reported, and several (full?) bricks.
--Chainfire
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
{
"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"
}
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
932e5f7a9f09c9bc33b14a527f642933
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads

Wow!... Looks great!
Wanna try after going back home!

I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?

Koush said:
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
Installation instructions:
Install Odin3
Start Odin3
Press PDU
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Click to expand...
Click to collapse
Can I assume this kernel wasn't compiled with ext3/4 support?

achio1115 said:
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Click to expand...
Click to collapse
I'm guessing, but considering this replaces the zImage that mimocan's fix provides anything you have on moved to ext3/ext4 will not be accessible.
To reverse reflash with the mimocan kernel.

Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do

Chainfire said:
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Click to expand...
Click to collapse
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.

damianarnold said:
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
Click to expand...
Click to collapse
I can confirm that, this mod won't work if you have mimocan's kernel applied.

Does it work if you "unapply" it ? Can you get your phone back functional again ?

cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it

raspdeep said:
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
Click to expand...
Click to collapse
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid

damianarnold said:
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
Click to expand...
Click to collapse
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.

Chainfire said:
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Click to expand...
Click to collapse
Every single app. you've installed will need to be reinstalled, it's as if the device is completely cleared of any settings/config.
Basically you need to restore from backup.

If you see this screen
follow these commands while odin3 is opened.
"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
Then flash this kernel to fix any slowness
http://android.eugenekay.com/Vibrant/LeshakKernel_9_01b9.tar
Eugenekay couldn't link because he only has 4 posts so I'm doing it for him
This might not apply to i9000 users but I posted it just encase.
Also any flashing done in odin formats everything. That is why recovery is needed in order to try and get zip updates. Zip updates wont allow a whole rom flash just modifications.

@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.

so are there gonna be roms in zip ?
or this recovery is gonna handle tars as well?

buddy01 said:
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
Click to expand...
Click to collapse
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).

not working on JF7, keeping on rebooting

Chainfire said:
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
Click to expand...
Click to collapse
fair enough.

hkfriends said:
not working on JF7, keeping on rebooting
Click to expand...
Click to collapse
Does the same thing on JG5...
When I first applied it, it rebooted itself twice in a row and booted fine. It ran for a good few hours... restored apps. from titanium backup. Did a reboot again. (just to be safe.) At that point, it kept rebooting itself... and then I pretty much gave up and flashed the stock JG5. (couldn't head to work w/o a working phone, lol) Anyone got it to work so far?

[Q] Lose Root after Nov 13 Update with WiFi Calling?

Our GS2 and the Amaze 4g are getting an update Nov 13 that will add WiFi Calling. I was wondering if we would lose the existing root and will have to re-root, or what precautions to take? Any tips?

I believe if you're rooted and have deleted some bloat.. you will not receive the ota.. may have to wait for the release and pull the apk so we can get wifi calling goodness..
Sent from my SGH-T989

Ah Crud, The only thing I have uninstaleld with Titanium Backup (I do not have pro so had to uninstall instead of freeze, but I did back it up) was the Tethering Manager so my tethering would work since they pulled some shenaningans on tethering and went ninja on customers tryingto charge them now. Would I hve to restore that then do OTA then uninstall again?
Back to the original question, would my root remain intact so I can go ahead and uninstall right after the OTA? Or would I have to re-Root?

If you made a Nandroid backup before you flashed SU...why don't you just restore that?

I did make a nandroid, does restoring that restore apps and app data to that point? Basically would I lose any apps I have installed since nandroid and its data?

manolodf said:
I did make a nandroid, does restoring that restore apps and app data to that point? Basically would I lose any apps I have installed since nandroid and its data?
Click to expand...
Click to collapse
Yes and yes. You will lose any data/apps you have installed/made after the nandroid backup. My suggestion is to do this before the update.

after removing "tethering manager" can one use simultaneous data on device and phone?
@manolodf after removing tethering manager can you use wifi tether and data on the actual phone simultaneously? While using a MyTouch 4g i was able to accomplish that feat but note i can't replicate on the galaxy s2, i already pay the 14.99/mo but will root and remove that tethering manager if it could enable me to use data on both the wifi tethered device and my phone simultaneously.

@ggfb20 I also came from the MT4G and yes I remember that ability, I do think after removing tethering manager that it is possible, though I cannot tell you with 100% accuracy, but what I can tell you that I did notice since is that the prompt warning you about not being able to use it simultaneously is now gone.
-- I just enabled hotspot and then opened web browser and it worked, so I would be very likely to say that it does work, I just did not have any device actually connected to the hotspot at the same time.

If your rooted you wont be able to take the ota anyway. You have to have the stock recovery to flash or it just errors. Someone will have a rooted rom posted the day of the ota so I wouldn't worry about it.
Sent from my HTC Glacier using XDA App

Ok, primarily my main concern is the WiFi Calling, so I just want to make sure i can either get APK or whatever other bug fixes etc in a rom. Hopefully I wont have to do a full wipe though, thats annoying!

manolodf said:
Ok, primarily my main concern is the WiFi Calling, so I just want to make sure i can either get APK or whatever other bug fixes etc in a rom. Hopefully I wont have to do a full wipe though, thats annoying!
Click to expand...
Click to collapse
If you're going to a different you're gunna have to do a full wipe no matter what...to avoid endless bootloops.

thanks for the info...
I can't wait to root now...well just a little, Ill do so shortly after getting that update on the 13th of November.

I had to retire my G S2 till the WiFi update comes out because I have no Tmobile service at my house. I rooted the S2 but I am positive someone will post the apk that we can install as soon as it come out.
Sent from my HTC Sensation Z710e using xda premium

In case you missed it!
We now have stock recovery thanks to buddy323
So we can go back to stock, to take the update, if we want.
Probably not necessary, I'm sure it will be posted here soon after the update.
[ROM] SGH-T989 // UVKID // Stock // Deodexed // Rooted //Busybox (
{
"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"
}
1 2 3 ... Last Page)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Kernel // UVKID (
1 2 3)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Recovery (
1 2)
Originally Posted By: bubby323
Don't forget to thank bubby! Even better donate! No better way to say thank you!

jangst123 said:
In case you missed it!
We now have stock recovery thanks to buddy323
So we can go back to stock, to take the update, if we want.
Probably not necessary, I'm sure it will be posted here soon after the update.
[ROM] SGH-T989 // UVKID // Stock // Deodexed // Rooted //Busybox (
1 2 3 ... Last Page)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Kernel // UVKID (
1 2 3)
Originally Posted By: bubby323
[STOCK] T-Mobile Samsung Galaxy S II Stock Recovery (
1 2)
Originally Posted By: bubby323
Don't forget to thank bubby! Even better donate! No better way to say thank you!
Click to expand...
Click to collapse
Very Useful.

manolodf said:
Ah Crud, The only thing I have uninstaleld with Titanium Backup (I do not have pro so had to uninstall instead of freeze, but I did back it up) was the Tethering Manager so my tethering would work since they pulled some shenaningans on tethering and went ninja on customers tryingto charge them now. Would I hve to restore that then do OTA then uninstall again?
Back to the original question, would my root remain intact so I can go ahead and uninstall right after the OTA? Or would I have to re-Root?
Click to expand...
Click to collapse
Tether manager has nothing to do with the ota. To state it clearly root = no ota. But do not worry. Do not run and unrooted your phone. Do not panic. What ever the update does some one will post it so rooted users can get it. It was the same for the Vibrant.

can i still update if i rooted my phone and i froze the bloatwares? or do i need to un-freeze them?

If you do not have the stock recovery you can't update via ota. You will have to either flash the stock recovery or wait til someone roots it and posts it.
galaxys2noobs said:
can i still update if i rooted my phone and i froze the bloatwares? or do i need to un-freeze them?
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App

ntellegence said:
Tether manager has nothing to do with the ota. To state it clearly root = no ota. But do not worry. Do not run and unrooted your phone. Do not panic. What ever the update does some one will post it so rooted users can get it. It was the same for the Vibrant.
Click to expand...
Click to collapse
Root does nothing to stop OTA updates. You will probably lose root if you run the update, but root does not stop it.

You might get the notification and download but without stock recovery it will not flash.
Astitious said:
Root does nothing to stop OTA updates. You will probably lose root if you run the update, but root does not stop it.
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App

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..

My S3 says "upgrading" all the time

After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?

MickeyS said:
After updating the phone with an ATT update, every time I restart or boot up my device it says that "Android is upgrading". Does anyone have the same issue? How do I get rid of that?
Click to expand...
Click to collapse
I suspect that the update didn't go quite right. It says that when the system is rebuilding your cache/dalvik cache. It sounds like maybe one or both of those is getting cleared when you shut down or they may not be getting built properly in the first place. I'd suggest backing up whatever you care about and doing a factory wipe. It can be a bit of a pain, but it'll probably solve your problem.
Also, bring on the details yo. Phone? Android version you came from/upgraded to? Aaaaaanything at all.

I has Android 4.0.4 and the latest update. It's a rooted phone and AT&T is my provider.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.

smartnphone said:
Are you running a custom ROM? I agree, you should do a factory reset. Just be sure to back up your data beforehand.
Click to expand...
Click to collapse
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.

MickeyS said:
No, I am not running a custom rom, all I have done to the phone is root it. What's the best way to back up your data? I useTitanium backup. How do I do a factory reset? I am new to the Android world and don't know much, any help will be greatly appreciated.
Click to expand...
Click to collapse
What phone do you have? Titanium backups are fine. Make sure the backups are on an external SD card or get them off the internal flash. If you need to shuffle files around, you can use ES File Explorer but BE CAREFUL if you give it root privs for some reason. No offense, but since you're kinda new to this if you screw up and erase the wrong thing, stuff's gonna break. Without knowing who makes your phone, the best I can tell you is to go into settings and dig around for the factory reset. Good luck!

I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...

He has said a S3 and ATT...I don't understand your question of what phone does he have?
Sent from my SGH-I747 using Tapatalk 2

m3741 said:
I don't mean to be a jerk, but for god sake man/woman/person... For the 3rd time, what phone do you have? And yes, that's a good possibility...
Click to expand...
Click to collapse
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2

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

Edit: ignore post.

corythug said:
He did say s3 att my man.... And if not its in the s3 forum so it'd be a safe assumption it'd be an s3, and carrier for the steps he needs is regardless.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Apologies... I'm blind as hell apparently. No more late night XDA...

MickeyS said:
I fixed the first problem with the factory reset but now I can't connect the phone to my Mac using Android file transfer. Could the update had something to do with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Like the other guy said, the update could be a possibility.
Reminds me when I had iPhones before I discovered Android. If you wanted to stay jailbroken, you'd have to make sure it's safe to do so before you update. Like you had to make sure it was iTunes safe, etc.

Did you install Google wallet?
Sent from my SAMSUNG-SGH-I747 using xda premium

So if AT&T has an update and your phone is rooted, don't update? I went ahead and updated without thinking about it. I am an iPhone user and didn't think that ATT had anything to do with Android OS. I took care of the upgrading issue, before the update I was able to use Android File Transfer with my Mac and I would connect to the phone, now forget about it. I can only do it now using VMware Fusion. Kies works but it's kind of limited. My next thing will be to install a ROM, but I can't find exactly what kind of phone I have. I know it's a Galaxy S3 from AT&T.
This is the information:
{
"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"
}
http://forum.xda-developers.com/attachment.php?attachmentid=1402926&stc=1&d=1350272265
What kind of specific rom's I have to look for, I've herd that if you install the incorrect rom you will brick your phone.

Im not very familiar with mac or iOS but your problem sounds like a driver issue on the mac, not android. Is usb debugging enabled by chance? Settings>developer options>android debugging....if its on try turning off then reconnect your phone. If its off try turning it on and reconnect and see if it changes. Beyond that i would suggest deleting any samsung/android usb device druvers from the mac and reinstalling....although someone with more iOS experience will have to offer some advice in exactly how to do that if you dont know, i certainly dont.
As far as installing AT&T OTA updates with root, its generally not a good idea, especially if you do install a custom ROM. Even on a stock rooted ROM there is a pretty good chance the update will 'fix' your root access and if you are on a custom ROM there is probably an even better chance of screwing up the operating system to the point that it doesn't boot properly, or even brick. Only install updates to your ROM from the developer, and follow any instructions they give on how to apply the update.
Lastly, you are looking for AT&T i747 roms and you also have to pay attention to which version of android you are on as to how you go about installing the ROM. For instance if you are running the stock AT&T ROM and try to install an AOSP based rom without formatting the device you are more than likely to have all kinds of issues, IF the OS even boots properly. I would suggest you take some time to read up and become familiar with the terminology, differences in versions, etc with android before you just dive in. If you are unsure about something ASK SOMEONE...much better to look like a noob than standing in line at AT&T with a bricked phone.

I was under the impression that all of these show that when rebooting, its just a matter of how long it shows this message. I dont think anyone with a stock rom does NOT see this when they boot for a couple of seconds.

Any good place to begin looking for stock ROMS?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

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