Develop Bugs

E971-Rogers-Stock ROM 4.0.4 with Bloat Removed.

Hey all you Rogers LGOG fans,
The wait is over. We are releasing our carrier/bloat-free LGOG Stock 4.0.4 ROM. This ROM has a few other modifications as well, which you can find below however, this ROM is essentially stock, flashable, updateable to JB(Pending bootloader unlock retention) and bloat-free. This ROM is also rooted so you won't have to do it again. Below you will see my changelog and development notes. Before we start going flash happy, I would like to extend a warm thanks to Nottach for his "The Base ROM" on the AT&T variation of our device, which was used as a base for this ROM, as well as the entire Team Codefire for unlocking our bootloader and getting the first CMW on the device. Now the fun stuff:
Disclaimer:
WE TAKE NO RESPONSIBILITY TO ANY DAMAGE, BRICKING or OTHERWISE IRREVERSIBLE CHANGES TO THEIR PHONES. YOU PROCEED NOW AT YOU'RE OWN RISK.
Brought to you by:
Team Codefire
Nottach
Shoreline Developments
PART 1: Root and Unlock Bootloader
1. Visit http://forum.xda-developers.com/showthread.php?t=1886460 for Rooting instructions thanks to Bin4ry
2. Visit http://forum.xda-developers.com/showthread.php?t=2007961 for Bootloader unlocking instructions thanks to Shelnutt2 and Team Codefire
PART 2: The ROM
1. Download our ROM and place it on the internal storage
2. Boot into recovery (Don't worry about wiping the aroma installer will do the hard work for you)
3. Make a BACKUP of your current ROM
4. flash our ROM and reboot (Make sure you flash from internal storage)
That's it! Now you're bloat and carrier free while still being able to enjoy all the features of stock.
Changelog - v1.0 (Based off of "The Base 0.6.5")-Dec 5, 2012
- Root
- BusyBox
- Deodex App Folder
- ZipAligned
- DeBloated
- Includes unlocked Rogers Boot Image
- Nexus 4 Boot Animation
- Removed Shutdown Animation
- Silenced Boot / Shutdown
- Increased WiFi Scan Interval
v1.1-Dec 6, 2012
- Replaced the unlocked Rogers Boot Image with the original FreeGee unlocked Boot Image
Bugs
None Reported Yet.
DOWNLOAD
ROM - Will be back shortly - Just cleaning up code and testing the new build

Thank you so much for posting your Rom. I hope the development for this phone will soon carry along... great work!
Do you know if this is cross carrier compatible?
Sent from my LG-E973 using xda app-developers app

kwf1 said:
Thank you so much for posting your Rom. I hope the development for this phone will soon carry along... great work!
Do you know if this is cross carrier compatible?
Sent from my LG-E973 using xda app-developers app
Click to expand...
Click to collapse
No Problem! With the devs working together, I think it will take right off. It's a Mako
I want to say yes that it's cross carrier compatible but I can't for sure. PM me you're rooted and unlocked and maybe we can take a look at a few things to see.

Dumb question probably, put zip in /sdcard
booted into CWM,
flashed from internal storage
went through aroma, rebooted
still seeing the lg logo at and don't see any changes of the base
wondering if i did something wrong?
let me know and thanks for the time and effort you put into this

BloodBaron said:
Dumb question probably, put zip in /sdcard
booted into CWM,
flashed from internal storage
went through aroma, rebooted
still seeing the lg logo at and don't see any changes of the base
wondering if i did something wrong?
let me know and thanks for the time and effort you put into this
Click to expand...
Click to collapse
Hmm that's strange for sure. Verify that you're carrier apps are gone. If they are then let me know and something didn't take with the bootscreen. If you still have them, reflash with the method above and let me know if it worked the second time around.
I'll be away from the computer for a couple hours. Talk to you soon!

Oooo! Very excited for this. This is one of the times where I hit download then started reading what all was included.
Flashing momentarily. Thanks guys!

tried with the touchrecovery, went through aroma, was stuck at settimg simlink, went downstairs came back phone was turned off, tried to turn it on and now nothing happens. weird
plug phone in usb
lg logo comes on for a sec
screen turns off
loop
last i check batter was at 56%
without usb or ac phone will not turn on either
well hello there sexy, i can get to the download mode at the very least
and now fastboot, but i cant get into recovery

BloodBaron said:
tried with the touchrecovery, went through aroma, was stuck at settimg simlink, went downstairs came back phone was turned off, tried to turn it on and now nothing happens. weird
plug phone in usb
lg logo comes on for a sec
screen turns off
loop
last i check batter was at 56%
without usb or ac phone will not turn on either
well hello there sexy, i can get to the download mode at the very least
and now fastboot, but i cant get into recovery
Click to expand...
Click to collapse
I'm in a similar boat unfortunately. I just freshly unlocked it with the freegee one click app since I wanted to support this kind of stuff when I shut down it started up again right away as if I had pressed restart instead of shutdown. It briefly showed the lg logo then turned off the screen then brought it back on but only displaying black. That's where it sat until I did the equivalent of a battery pull by holding the power button for a really long time. I started it up again, this time holding volume up as well as power and got to fastboot and from there to the recovery. Flashed after that, no problems came up. Then it did the same thing it did the first time with the lg logo, screen off for a second, then black.
What now? o_0
I've already tried flashing it again over top of it so now I'm going to give restoring from backup a shot.
I'll let you know how that goes.
EDIT: Hmm... not good. I can attempt to restore but I get a MD5 mismatch.

Zachariasmith said:
I'm in a similar boat unfortunately. I just freshly unlocked it with the freegee one click app since I wanted to support this kind of stuff when I shut down it started up again right away as if I had pressed restart instead of shutdown. It briefly showed the lg logo then turned off the screen then brought it back on but only displaying black. That's where it sat until I did the equivalent of a battery pull by holding the power button for a really long time. I started it up again, this time holding volume up as well as power and got to fastboot and from there to the recovery. Flashed after that, no problems came up. Then it did the same thing it did the first time with the lg logo, screen off for a second, then black.
What now? o_0
I've already tried flashing it again over top of it so now I'm going to give restoring from backup a shot.
I'll let you know how that goes.
EDIT: Hmm... not good. I can attempt to restore but I get a MD5 mismatch.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010624
attempting this atm
dont think this worked

BloodBaron said:
http://forum.xda-developers.com/showthread.php?t=2010624
attempting this atm
dont think this worked
Click to expand...
Click to collapse
Bleh. Hmm... think we both could have, by some coincidence, had a bad download? I was going to try and flash it again but sideloading the zip this time but I switched to a new computer recently and need to set up adb and stuff again. The other thing I was wondering too was about wiping the data partition. This was brought on by this step in the unbricking instructions you linked me to.
potatohead said:
8) If the phone is stuck at the booting up LG/Telco logo, you will need to manually wipe the data partition.
Click to expand...
Click to collapse
I'm coming to this phone from a nexus which was dead simple and straight forward when it came to partitions and having an internal sd and just regular internal memory. This phone just has internal memory, right? So wiping data is going to wipe everything everything, right?

Updated Zip
Seems the unlocked Rogers boot image is causing some grief - I didn't seem to run into this issue on mine. I flashed through CWM that came with freegee. I have updated the zip file with the original freegee unlocked boot image which should solve the problem. The new zip is uploading now and will be ready shortly, I've gone and taken down the previous build and apologize for the inconvenience.

ShorelineDroid said:
Seems the unlocked Rogers boot image is causing some grief - I didn't seem to run into this issue on mine. I flashed through CWM that came with freegee. I have updated the zip file with the original freegee unlocked boot image which should solve the problem. The new zip is uploading now and will be ready shortly, I've gone and taken down the previous build and apologize for the inconvenience.
Click to expand...
Click to collapse
Ah, superb. It's 1am here where I am now and was getting worried about having to sleep before fixing this. Thanks for getting a fix out so fast, Shoreline! I'll let ya know if it fixes things.
EDIT: Does the link in the first post need to be changed? Or is it just uploading still?

Zachariasmith said:
Ah, superb. It's 1am here where I am now and was getting worried about having to sleep before fixing this. Thanks for getting a fix out so fast, Shoreline! I'll let ya know if it fixes things.
EDIT: Does the link in the first post need to be changed? Or is it just uploading still?
Click to expand...
Click to collapse
Sorry, having to deal with dropbox isn't always fun when it comes to uploading such a large file but it'd done and the thread has been updated. I hope this works as tested on my device.
Let me know how this goes for you folks!

Zachariasmith said:
Ah, superb. It's 1am here where I am now and was getting worried about having to sleep before fixing this. Thanks for getting a fix out so fast, Shoreline! I'll let ya know if it fixes things.
EDIT: Does the link in the first post need to be changed? Or is it just uploading still?
Click to expand...
Click to collapse
let me know how and if you fixed your phone and ill do the same
my issue now is that i cant get the phone to reboot with the power button

BloodBaron said:
let me know how and if you fixed your phone and ill do the same
my issue now is that i cant get the phone to reboot with the power button
Click to expand...
Click to collapse
Hmm... I may be a while. It seems I can't even get into recovery now. I don't know how that happened since I could last night. Is there a way to push the phone into recovery mode by way of adb?
Crap, now I'm starting to actually get scared since I can't seem to get into anything.

First off thank you for all your work! This is awesome!
I flashed the rom with TRWP and everything went smoothly, it reboots fine. However it doesn't appear to actually do anything. Everything on my phone is the same. Even the rogers bloat apps are still there. I put the zip on /sdcard and flashed from there.
Any help would be much appreciated!
Thank you!

Zachariasmith said:
Hmm... I may be a while. It seems I can't even get into recovery now. I don't know how that happened since I could last night. Is there a way to push the phone into recovery mode by way of adb?
Crap, now I'm starting to actually get scared since I can't seem to get into anything.
Click to expand...
Click to collapse
alright heres what i did
restored with kdz as per the unbrick thread
except when i reached lparam=95 it woot reboot into the bootloop
so when it did that i pressed the up and down volume button and it rebooted into download mode
still wsnt working
brought my phone into the rogers store
the guy plugged it in a power supply and he must have tried putting it in recovery because it went into the factory recovery menu and he was able to boot normally
all i lost really was root and unlocked bootloader
not sure why he was able to get it to work and i wasnt oh well
if u need help with the kdz let me know i am more than happy to help

BloodBaron said:
alright heres what i did
restored with kdz as per the unbrick thread
except when i reached lparam=95 it woot reboot into the bootloop
so when it did that i pressed the up and down volume button and it rebooted into download mode
still wsnt working
brought my phone into the rogers store
the guy plugged it in a power supply and he must have tried putting it in recovery because it went into the factory recovery menu and he was able to boot normally
all i lost really was root and unlocked bootloader
not sure why he was able to get it to work and i wasnt oh well
if u need help with the kdz let me know i am more than happy to help
Click to expand...
Click to collapse
Haha, okay I was just about to give the kdz thing a go. I shouldn't have any problem with the taking it in to Rogers bit as I'm actually doing this at work right now. (I work as a Rogers rep. )

Zachariasmith said:
Haha, okay I was just about to give the kdz thing a go. I shouldn't have any problem with the taking it in to Rogers bit as I'm actually doing this at work right now. (I work as a Rogers rep. )
Click to expand...
Click to collapse
bahaha awesome apparently you guys are wizards and touching my phone fixes it

BloodBaron said:
bahaha awesome apparently you guys are wizards and touching my phone fixes it
Click to expand...
Click to collapse
Haha, yup. That's definitely happened to me before too. I'm just in the process of using the kzd tool. It gives me a runtime error right away though, but it doesn't seem to stop if I don't click it. I'm going to try letting it keep running and see what happens.
EDIT: Aaaaaand we're back! Up and running again but it looks like root is gone and bootloader is relocked as expected. Time to try again!
EDIT EDIT: Okay, I told myself I would stay away for a little bit after that scare and stay stock but I can't hold myself back. Flashing... rebooting... looks like its booting! Uh, yay?
First off thank you for all your work! This is awesome!
I flashed the rom with TRWP and everything went smoothly, it reboots fine. However it doesn't appear to actually do anything. Everything on my phone is the same. Even the rogers bloat apps are still there. I put the zip on /sdcard and flashed from there.
Any help would be much appreciated!
Thank you!
Click to expand...
Click to collapse
This is the same problem I'm having now. :/

stuck at Samsung Logo Note 2 ATT

Stuck on the samsung logo.
The battery drained dead, and I waited until I got home to charge it. I plugged it in and the grey battery popped up and a loading wheel, but it froze.
Now it doesn't turn on. I switched batteries and it goes to the samsung logo and sits there. I tried VolUP+VolDown+HOME+Power and All the other button combos and still nothing just goes to samsung screen and reboots, then I notice the led light flashes red very faintly and once quickly then the logo comes back up.
Any ideas?

Did you root or install custom recovery?

kirkla79 said:
Did you root or install custom recovery?
Click to expand...
Click to collapse
No I haven't tried to do anything of the sort. I just got this phone when it got released, and haven't explored that much with it yet. It just suddenly doesn't work after the battery drained dead.

I would just go back from where you bought it a get it exchanged then.

kirkla79 said:
I would just go back from where you bought it a get it exchanged then.
Click to expand...
Click to collapse
Yeah I'm just going to hate to lose everything because I couldn't do a backup...
Sucks.

Root install recovery and clear cashe partition and dalvik cashe. Use stock rom image with SU injected and do not wipe. Or exchange and loose everything
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

My girlfriend drained her battery until the phone shut off. Had to leave it on the charger for almost an hour before it would boot. I thought it should boot as soon as I plugged it in but that's not the case. Try letting it sit and charge for awhile.

jethro650 said:
My girlfriend drained her battery until the phone shut off. Had to leave it on the charger for almost an hour before it would boot. I thought it should boot as soon as I plugged it in but that's not the case. Try letting it sit and charge for awhile.
Click to expand...
Click to collapse
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?

PrestigeA said:
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
Click to expand...
Click to collapse
Not sure your going to be able to root with a non-booting phone. Here are a couple links about rooting
Chainfire's method you need download mode
mrRobinson's root injected stock Roms, also need download mode
Good luck hope one of these works for you.

Just my $0.02 worth.
My suggestion is make sure you are using the original, Samsung battery. Let it charge for 8 - 10 hours. Take it off the charger, remove the battery from the phone, wait several minutes; then replace the battery and try to boot.
If that doesn't restore, I'd take it back to the store from which you purchased it, and see if a new, oem battery will let it boot. The store should try to do everything they can to help, short of replacing the phone. But it may just be your phone has gone bad -- in which case rooting isn't going to help...
Good luck.
PrestigeA said:
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
Click to expand...
Click to collapse

Intall CWM with odin then reboot in recovery and install stock rooted .zip or stock based ROM. Its called a dirty install. You can do this by placing the .zip in a microSD then install from external in CWM. You will end up with all your old crap but the .zip will replace your corrupted files. I recommend you save everthing as soon as it boots and yhen do a clean install of whatever ROM you want even if its stock.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

reinstalled stock ROM, stuck on logo
I recently got an AT&T note 2. I rooted and installed cwm recovery. I tried installing Android Revolution HD 5.0 after running their superwipe script. Everything went smoothly except the SIM was not recognized. I couldn't get it to work so I tried 2 other ROMs and I had the same issue. I decided to go back to stock and wait for Cyanogen to release a ROM.
The issue I am having now is that the stock ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2004650 and another stock ROM (KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar) won't boot. I can successfully push them to the phone from Odin, but then they reboot and get stuck on the Samsung logo. The phone doesn't give any error messages, no strange leds on, no reboots, it just sits there with the Samsung logo pulsing. I can still boot into the download mode (vol down, home, power).
Any advice on how to get to a functoning ROM? At this point I don't care if it is stock or custom, I just need something that works. Any help would be greatly appreciated!

cdt710 said:
I recently got an AT&T note 2. I rooted and installed cwm recovery. I tried installing Android Revolution HD 5.0 after running their superwipe script. Everything went smoothly except the SIM was not recognized. I couldn't get it to work so I tried 2 other ROMs and I had the same issue. I decided to go back to stock and wait for Cyanogen to release a ROM.
The issue I am having now is that the stock ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2004650 and another stock ROM (KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar) won't boot. I can successfully push them to the phone from Odin, but then they reboot and get stuck on the Samsung logo. The phone doesn't give any error messages, no strange leds on, no reboots, it just sits there with the Samsung logo pulsing. I can still boot into the download mode (vol down, home, power).
Any advice on how to get to a functoning ROM? At this point I don't care if it is stock or custom, I just need something that works. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You should only flash ROMs from the "AT&T Galaxy Note II Android Development" section. I think Revolution HD is not an AT&T ROM, I don't know about the other ROMs you flashed (as you didn't say what they where). Those ROMs probably flash a non AT&T compatible radio on you phone. You should read and re-read and make sure you know what to do and what ROM can can flash before you start flashing.
Do you have a custom recovery installed, CWM or TWRP? Have you tried using a different computer and different cable?
Maybe try flashing the AT&T modem and them a correct ROM and see if that helps. Honestly, I'm not sure how to help you beyond that.
Good luck...

Back up and running
RojasTKD said:
You should only flash ROMs from the "AT&T Galaxy Note II Android Development" section. I think Revolution HD is not an AT&T ROM, I don't know about the other ROMs you flashed (as you didn't say what they where). Those ROMs probably flash a non AT&T compatible radio on you phone. You should read and re-read and make sure you know what to do and what ROM can can flash before you start flashing.
Do you have a custom recovery installed, CWM or TWRP? Have you tried using a different computer and different cable?
Maybe try flashing the AT&T modem and them a correct ROM and see if that helps. Honestly, I'm not sure how to help you beyond that.
Good luck...
Click to expand...
Click to collapse
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!

cdt710 said:
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
Click to expand...
Click to collapse
Excellent, glad you were able to get it working.
Enjoy!

cdt710 said:
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
Click to expand...
Click to collapse
get yourself a jig dude, if you were really stuck you could have just put that badboy in and it would take you to dl mode, from there you could have odin'd yourself anywhere you wanted to. A thought for next time you get yourself into a situation you think isn't recoverable.
if you are a in a bloop you can usually get to recovery and from there sort yourself out. I know you are ok now, but this may still help someone else.
A jig is like a condom... protection even if you think you don't need it, you should prolly use it.

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

In case of emergency!

Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?

Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app

lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.

heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download

Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.

Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!

frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2

Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!

frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2

Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing

Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!

http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?

Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)

ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

[Q] Samsung t989 Galaxy S II - Bootloop HELP please :(

I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!

still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?

phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.

zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.

If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?

JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.

sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!

dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know

sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.

JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.

sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.

JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!

sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:

Root issue/ unbootable

I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Edit: 1:34
Sorry the rest of the photos didn't upload, I will upload them later.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app

MzzSarahx3 said:
I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you tried using a different battery? Is the battery a samsung stock battery? Is the battery physically flat or is it swollen? Have you done a battery pull and then attempted to boot the phone? If you have a external charger, fully charge the battery (unless the battery is swollen or damaged).
You might also boot into recovery and try charging from there. Recovery has it's own kernel and it is not altered much from what I can tell. I use twrp and it shows when the battery is charging. I'd use twrp 2.6.3.x as it is proven while 2.7.0.0 is freshly released.
Can you boot into recovery and pull a Nandroid? If so, do so. If recovery is stable (and you have adequate battery charge) try to flash a T889 TW rom and see if a stock kernel and firmware will allow the battery to charge.
Hastily spouted for your befuddlement

MzzSarahx3 said:
I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your device's battery with other one . I think your old battery makes all the trouble .
Or Just make sure if your device got virus infection . That may also cause this same problem . Better idea is contact your device's dealer . They can fix your device .
Click :thumbup: button if this answer is helped you
Sent from my GT-S7562 using XDA Premium 4 mobile app

Nvm...edited

I'm here to report that my phone is most likely bricked. I tried installing different roms and kernels through my external sd card but none of them would boot. Out of pure stupidity, I flashed a different recovery on my phone and from there I probably killed all chances of saving my phone. It is now unable to boot into recovery and unable to be recognized by ODIN.
Any further suggestions are again appreciated.

MzzSarahx3 said:
I'm here to report that my phone is most likely bricked. I tried installing different roms and kernels through my external sd card but none of them would boot. Out of pure stupidity, I flashed a different recovery on my phone and from there I probably killed all chances of saving my phone. It is now unable to boot into recovery and unable to be recognized by ODIN.
Any further suggestions are again appreciated.
Click to expand...
Click to collapse
Does your phone boot in to download mode ?

ciphercodes said:
Does your phone boot in to download mode ?
Click to expand...
Click to collapse
Yes it does go into download mode but isn't recognized by Odin.

MzzSarahx3 said:
Yes it does go into download mode but isn't recognized by Odin.
Click to expand...
Click to collapse
If you get ODIN working then the device can be recovered by flashing back to stock.
1) Did ODIN work for your device before this issue ?
2) Did you already try updating drivers, different cable etc etc.
How about Heimdall, check if it recognizes your phone.

ciphercodes said:
If you get ODIN working then the device can be recovered by flashing back to stock.
1) Did ODIN work for your device before this issue ?
2) Did you already try updating drivers, different cable etc etc.
How about Heimdall, check if it recognizes your phone.
Click to expand...
Click to collapse
This sounds strangely similar too what happened with my phone. Worked fine and then next day dead.
By any chance did you install Jedi Rom? That was the Rom i was using before mine died.

nollington said:
This sounds strangely similar too what happened with my phone. Worked fine and then next day dead.
By any chance did you install Jedi Rom? That was the Rom i was using before mine died.
Click to expand...
Click to collapse
I have used the Jedi Rom but I was using the beanstalk rom. The symptoms sound a lot like sudden death syndrome but my phone was sent in and fixed for that.
To be exact about Odin and Heimdall does recognize my phone but trying to install anything will give u this error : "device not accessible."

MzzSarahx3 said:
I found my phone dead this morning and tried plugging it in. The screen reacted by showing a loading battery logo that seems to have froze. I booted into recovery and tried to factory reset but it shows that nothing is mounted. When trying to boot out of recovery it doesn't get past the galaxy note II screen. I've attached a picture of each screen I mentioned.
Prior to this, I was experiencing root issues. Titanium backup reported that I has a outdated binary I believe. I tried updating through super user but I would get an error. My phone has also been experiencing terrible battery life which I assumed was a kernel or rom issue, though it's clear that it wasn't. Regardless, I was running the beanstalk rom if anyone wanted to know.
Any help is appreciated, thanks.
Edit: 1:34
Sorry the rest of the photos didn't upload, I will upload them later.
Sent from my SAMSUNG-SGH-I957 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same problem. I used Odin and re flashed my phone. Try installing a new rom or the same one
---------- Post added at 06:01 AM ---------- Previous post was at 05:49 AM ----------
I had the same problem. try using ODIN and Re flash or re flash your ROM maybe use a new ROM