[q] kt747 aosp jb gs3 - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hello everyone. I flashed KT747 AOSP JB. CWM install it completelly, after reboot the phone passed the second samsung logo and just a black screen came on and nothing else happened for several minutes. Leaving the power button pressed or power, home, volume up just restarted the phone then going back to the black screen. During that time i was ****ting bricks "literally", I hard bricked this phone not long ago trying to install a rom, and i sent it to samsung in texas and after two long incomunicated weeks they fix it and send it back.
Finally I decided to remove the battery and reinstall it. Thank the almighty I was able to boot into cwm recovery and restore from stock backup.
PHEEWWW!!!! I came back to life. But im freaked out and i want to try this kernel.
Does anyone has a clue on what could be wrong?
I tried to post on the KT747 thread but since im new member they wont let me.
Thanks all in advance for your help

Search please.
This means your phone cannot handle the kernel. Done and done.
Sent from my A510 using Tapatalk 2

c_86 said:
Search please.
This means your phone cannot handle the kernel. Done and done.
Sent from my A510 using Tapatalk 2
Click to expand...
Click to collapse
I did search and I also read a lot. This kernel is supposed to be for At&t i747, which is the model that i have.
Thanks

Yes it is. But if you did really read a lot then you would know not all chips are made the same and some people have reported that the kernel doesn't work. And after a exchange for a new one/phone, it does work. Which simply means the hardware aka chip cannot handle a custom kernel. So you're stock with the stock kernel.
Sent from my A510 using Tapatalk 2

thanks

Related

[Q] Sprint Galaxy S III Rooted/Installed ROM... Now won't power on. Help!

Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.
Thanks I'll check there.
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium
New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...
bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2
matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.
Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.
Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2

[Problems back] daily reboots / warm reset - last_kmsg

Hi guys,
i'm running AOKP Build 3 , fresh install, Apps downloaded through the Play Store and restored data for some apps ( no system apps) via Titanium Backup.
But from time to time i notice hot reboots. I turn the screen off, but it will not get on again. After about 1-2 minutes the phone reboots ( i see the Boot animation).
Except all is running smooth. Also i tried the latest Franco Kernel, but same Problem.
Could someone look into the last_kmsg i pulled right after a hot reboot? Maybe a dev or someone with more knowledge than me can find the Problem.
Thx,
Ebi
https://www.dropbox.com/s/xvetw35abc8yti3/last_kmsg
Pastebin:
http://pastebin.com/wZ1JJVyW
What kernel are you using? And are you using supersu, or superuser? I had the same issue b4 random reboots, it seemed that the issue was root not sticking in and also the Franco kernel, think my phone didn't like it, I had to re-root and re-install cwm recovery, using the toolkit and that seemed to help, I had the issue with every ROM I flashed, hope It helps
Sent from my Galaxy Nexus using Tapatalk 2
I faced the constant reboot issue on stock JB... apparently, switching to CM10 or AOKP helped (I've stuck to AOKP since it contains the stock apps... sans the bugs present in all AOSP roms).
Are you sure it's a root problem? I'll go try it out now and check.
aeoveu said:
I faced the constant reboot issue on stock JB... apparently, switching to CM10 or AOKP helped (I've stuck to AOKP since it contains the stock apps... sans the bugs present in all AOSP roms).
Are you sure it's a root problem? I'll go try it out now and check.
Click to expand...
Click to collapse
I used the Stock AOKP Kernel, and later the Franco. And both had the same issue.
Will try suprakarmas way
It all points at the root not sticking with the Franco kernel app as well for some reason once I started messing with that sucker I started having the reboots, if the problem persist I advice to use the toolkit to reinstall stock ROM, re-root and reinstall custom recovery, I had teamwins but I went back to cwm, it all has been good am on android revolution HD am staying away from aokp and cm10 till there's a stable release
Sent from my Galaxy Nexus using Tapatalk 2
I was seeing a lot or partition remounts (not sure which one as it was listed as the physical block device) as well as an emergency read only remount in your log.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
I was seeing a lot or partition remounts (not sure which one as it was listed as the physical block device) as well as an emergency read only remount in your log.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Any idea what could cause this?
EbiEre said:
Hi guys,
i'm running AOKP Build 3 , fresh install, Apps downloaded through the Play Store and restored data for some apps ( no system apps) via Titanium Backup.
But from time to time i notice hot reboots. I turn the screen off, but it will not get on again. After about 1-2 minutes the phone reboots ( i see the Boot animation).
Except all is running smooth. Also i tried the latest Franco Kernel, but same Problem.
Could someone look into the last_kmsg i pulled right after a hot reboot? Maybe a dev or someone with more knowledge than me can find the Problem.
Thx,
Ebi
https://www.dropbox.com/s/xvetw35abc8yti3/last_kmsg
Pastebin:
http://pastebin.com/wZ1JJVyW
Click to expand...
Click to collapse
that log is from cm kernel??
Code:
[ 26.531280] Restarting Linux version 3.0.36-cyanogenmod-geb0f696 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Thu Jul 12 13:52:24 PDT 2012
what's going on? i thought we were dealing with aokp and/or aokp+franco.
No, this was after flashing Francos kernel. Don't know why it is not shown but maybe this was the problem, a bad flash?
What I did was rerooting the phone with the toolkit and re flash Francos kernel. No reboot till then, but what I noticed after switching the phone on this morning the cpu settings are gone. They are back at the defaults...
Is this a known issue?
Will report back after work.
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
ahem i wouldnt know. dont run aokp or cm right now.
i would advise you first to learn how to start fresh google way. forget toolkits. read efrant's stickies, they're in his sig. good, know you all about fastboot and adb basics.
reflash latest cwm non-touch. reflash aokp in cwm, you dont need to root to flash a rom. use it like that for a couple of days. no issues risen? reflash franco in cwm. this is how you troubleshoot.
sent from my i9250
So, it seems that for some reason, flashing the Franco kernel thru his app causes the reboots, and, either thru Google or toolkit, going back to stock, re-rooting or no need to do so, reinstalling cwm recovery solves the issue, at least on my end, just my 2 cents \„„/
Sent from my Galaxy Nexus using Tapatalk 2
Ok work is over and no reboots since about 20hours
I think the rerooting or the re flashing of the recovery, which is one step in rerooting, solved the problem.
Thx everybody
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
EbiEre said:
Ok work is over and no reboots since about 20hours
I think the rerooting or the re flashing of the recovery, which is one step in rerooting, solved the problem.
Thx everybody
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Click to expand...
Click to collapse
please edit the title thread with the [SOLVED] tag.
Hey guys,
me again.
The problems are back
I don't know why, but i don't get a rom to run more than 1 1/2 days without having a reboot.
Today i also tried the Odin Flash. So know i am running a stock Rom, just rooted. The whole day it was fine, i used my phone the normal way. But now i am back at home, and what? I pressed the power button to turn the screen off and instantly a second time to get it back, but it didn't come back. Black screen.. and some seconds later i see the Boot Animation.
After it was back i tried to find the last_kmsg, but it is not there in the stock Rom.
Is ther another place to find something like a log?
Hope to get some help
Cheers
Could someone tell me the most efficient method to go back to full stock, and reroot again?
Maybe i did something wrong during this process !? Everything i tried to do seems not to work :/
EbiEre said:
Hey guys,
me again.
The problems are back
I don't know why, but i don't get a rom to run more than 1 1/2 days without having a reboot.
Today i also tried the Odin Flash. So know i am running a stock Rom, just rooted. The whole day it was fine, i used my phone the normal way. But now i am back at home, and what? I pressed the power button to turn the screen off and instantly a second time to get it back, but it didn't come back. Black screen.. and some seconds later i see the Boot Animation.
After it was back i tried to find the last_kmsg, but it is not there in the stock Rom.
Is ther another place to find something like a log?
Hope to get some help
Cheers
Could someone tell me the most efficient method to go back to full stock, and reroot again?
Maybe i did something wrong during this process !? Everything i tried to do seems not to work :/
Click to expand...
Click to collapse
You should have edited thread title again, removing [SOLVED] tag; I just happened to come back because I wasn't sure if I had checked this one already or not.
/proc/last_kmsg should be there. How did you try getting it, adb or from a file explorer on the device? I'm at work so no adb here, but I've just checked and /proc/last_kmsg is there for me. Not sure if factory image from Google doesn't have it, but it should, I'm running my own build from JZO54K (android_4.1.2_r1), and I believe this is the closest to the factory image as it gets.
As for your last question, I already told you: read this thread.
bk201doesntexist said:
You should have edited thread title again, removing [SOLVED] tag; I just happened to come back because I wasn't sure if I had checked this one already or not.
/proc/last_kmsg should be there. How did you try getting it, adb or from a file explorer on the device? I'm at work so no adb here, but I've just checked and /proc/last_kmsg is there for me. Not sure if factory image from Google doesn't have it, but it should, I'm running my own build from JZO54K (android_4.1.2_r1), and I believe this is the closest to the factory image as it gets.
As for your last question, I already told you: read this thread.
Click to expand...
Click to collapse
Ok i found the last_kmsg but it is really big and i only See a line with omap and while no Data requested... Again and again.
Will have a closer look at it later and Maybe Post it from my PC.
But before that i will follow your guide and hope to solve the issue.
Btw good morning
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
I'm back, i followed the guide, did everything and just rooted my Phone. Except that everything is original.
More than 1 day i had no issues, but today... reboot. I didn't do anything, at first it happened in the morning at work, but i think it was not a "full" reboot, because in the about phone menu i saw a on time around 8 hours.
But later the phone was just lying at my table and suddenly i saw the boot animation. I have no idea what to do.
What i got is the last_kmsg, but it's really big again so i was just able to copy a little thing of it. I don't know how to find the exact time of the reboot so i hope it is inside this pastebin:
http://pastebin.com/raw.php?i=xZatKns5
Any ideas? Is the reboot shown there?
What i will try is to get a new sim, mine is very old, maybe this could be a solution!? Except i have no idea .. could it be a hardware issue?
Cheers
Edit: Just an idea, could it have something to do with the baseband? I read a lot of errors or something like that related to omap things.. !?
Can I suggest you they flashing another kernel - one with SmartReflex off? Faux's kernel (v22) works... so long as you have the version WITHOUT SmartReflex.
Well... it works for me. SmartReflex and my phone hate each other (it happened one, random day... no rhyme kr reason to its occurance). And I don't undervolt.
sent from my mini tractor
What exactly is smart Reflex?
Iam still running the Stock Rom just rooted and the Problem changed a bit . I did not have real reboots, 1-2 Times a Day the screen keeps beeing Black if i Switch it on. But After some seconds it is back and runs as if nothing happened. So not real a Reboot But a relatively long break...
Will wait for my New sim now...
Dont know if i should try a custom Rom till then.
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Smart Reflex is some automatic voltage/undervolting the kernel performs in order to save some battery. It comes enabled with the stock kernel... and for me, that's the cause of my reboots (and kmsg wasn't very helpful except for the fact that some MPU clock was being reset... and there's an option [to disable it] with the Smart Reflex parameters).
Soooo.... I turned it off altogether.
Rarely do I see blackouts for a second while my phone screen is on and I'm doing something on it. Before, it would reboot without warning.
If you're in the stipulated warranty timeframe, try getting it replaced and see if your new unit fixes it... else, try a new kernel.
PS: trickster mod is a very useful app... hint hint.
sent from my mini tractor

[Q] Bricked my phone after flashing new Kernel on top of Cyanogenmod 10

Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Boot in recovery now tgat you flashed stock rom. To boot in recovery press
Volume up+home button+on/off.
When samsung logo appears release the power button.
When it will boot in stock android recovery select wipe cache and wipe whole system (can't recall how it is written). Then select reboot now. That should do it.
Sent from my GT-N7100 using xda premium
mariosraptor said:
Volume up+home button+on/off.
Click to expand...
Click to collapse
That did not quite do it but I feel like a fool right now since this is the first time I realised that I mixed up Volume up and Volume down. But you gave me an option for that factory reset and after flashing CWM on top of that with ODIN it works again. One night wasted on nothing but my own lack of sleep and stupidity.
Thanks!
Good that it is working
Sent from my GT-N7100 using xda premium
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
SenK9 said:
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Anyway, glad it ended well for you OP!
Androssama said:
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Click to expand...
Click to collapse
Thanks! I haven't experimented much with custom kernels and my first try in combination with CM 10 didn't end that well. This gives me something to go from. Also I had a HTC Desire before and just got the Note 2 a few weeks ago, so there is another thing I have to get to know better.
Dude, please note that, for those kernels above which support both Touchwiz/Samsung and AOSP/Cyanogenmod based ROMS, there will be a separate version of the kernel for each.
hdr32 said:
Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Click to expand...
Click to collapse
As long as you can enter DOWNLOAD mode, your phone is NOT bricked. When you **** up your bootloader and stuff, then we can talk...
Hopefully this has taught you how important it is ti actually read up on something before you do it. Not only are the note2core and perseus kernels for samsung based roms only, other kernels such as redpill and neak only support the n7100 for their aosp/cm kernels.
As far as I know there is currently no other cm kernel for the n7105, although there is a neak cm kernel for the n7105 currently in beta testing.
Sent from my GT-N7100 using xda premium
No worries... learned my lesson... Sometimes I just need that smack in the face to get it.
And before I break my bootloader or some similar disaster occurs... I'll read first.
Sent from my GT-N7105 using xda app-developers app
Think we need a sticky with good instructions how to install and make a nandroid backup.
As well as sticky for EFS backup and why its so important to do it first and properly.
I know I had a lot of problems finding this info and implementing it proper,

Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)

After installing the rXTREME v6.2 ROM for the i9305, I selected restart from Recovery and it never turned back on. The battery was fully charged before I installed this custom ROM.
- I have removed the battery for an hour and then tried again turn it on - no success. Can't get into Download mode using the 3-buttons.
- When I plug it into my laptop via USB I hear the 'connected sound' and when I remove it I hear the 'disconnected sound', but I do not see any ability to access the phone via Windows Explorer. The driver is found and connected too.
- I tried using Odin and it say's "Added!" when I connect, but the COM:x field is 'yellow', not blue. (Keep in mind I can't get into Download mode on my phone, but I still tried with Odin) I load the right PDA file (I9305XXBMA3_I9305MEOBMA1_I9305XXBLL5_HOME.tar.md5) and have 'Auto Reboot' and 'F. Reset Time' checked. Odin message stays on status "SetupConnection..". I've left it this way many times, one time overnight. But with no success.
Any advice??? Please help :/
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
You are hard bricked. You flashed an international ROM to a us phone (or vice versa, your thread title is a little confusing on what device model you have)
JTAG or send to Samsung.
Sent from my SGH-I747 using xda app-developers app
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
I'm not sure he's hard bricked. Hard brick means no signs of life. Odin can see it, so there's obviously some sign of life. You need to find the proper stock firmware for your phone and try to flash back to stock
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
mrhaley30705 said:
I'm not sure he's hard bricked. Hard brick means no signs of life. Odin can see it, so there's obviously some sign of life. You need to find the proper stock firmware for your phone and try to flash back to stock
Click to expand...
Click to collapse
ODIN also detects hard bricks. It usually shows up as an unknown device with no drivers and can't be flashed. I've been there and done that with my own hard brick.
As his post says his phone won't boot, even after a battery pull and can't get into download or recovery. That would be no signs of life.
I have seen it happen too many times with people flashing international ROMs to their us devices. 95% of the time it is always a hard brick.
Unless he provides us with an update showing that the phone can boot, at all, even a flicker of the screen, its a dead phone. =/
Sent from my SGH-I747 using xda app-developers app
bshend said:
rXTREME v6.2 ROM for the i9305
Click to expand...
Click to collapse
if the phone won't turn on by any mean... you got yourself hard bricked.
people should really read before they actually flash a new rom... what you flashed is an international version.
but that's also weird... if i recall, some people mentioned when they flash international roms, they only got themselves soft bricked..
Re: Galaxy s3 i9305 won't turn on after installing custom rom (AT&T LTE 4G version)
pcshano said:
if the phone won't turn on by any mean... you got yourself hard bricked.
people should really read before they actually flash a new rom... what you flashed is an international version.
but that's also weird... if i recall, some people mentioned when they flash international roms, they only got themselves soft bricked..
Click to expand...
Click to collapse
I concur. Too many people gloss over the thread to flash whatever they feel like it. (even saw people using a vzw app to unlock their att boot loader.. which isn't even locked. also hard bricked. )
The lucky few do get a soft brick. Those lucky few were able to see the Samsung boot logo though. It all depends on the ROM. For instance if you flash the international foxhound ROM its a guaranteed brick. 3 different people in a 2 day span I helped not too long ago. all flashed foxhound all hard bricks.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
I concur. Too many people gloss over the thread to flash whatever they feel like it. (even saw people using a vzw app to unlock their attack boot loader.. which isn't even locked. also hard bricked. )
I really feel XDA should implement a test on reading comp and flashing basics before you are allowed access to dev forums for ROMs.
The lucky few do get a soft brick. Those lucky few were able to see the Samsung boot logo though. It all depends on the ROM. For instance if you flash the international foxhound ROM its a guaranteed brick. 3 different people in a 2 day span I helped not too long ago. all flashed foxhound all hard bricks.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
people should really do research before actually doing it in any way.
Do you get any signs of life on the screen at all? Either Recovery or Download mode? The Galaxy S3 splash screen? Anything at all?
If not, then it's a hard brick and you can get it repaired via a JTAG service (check eBay).
However, if you get ANY signs of life on the screen at all, even if for just a moment, then you might be able to repair things yourself.
innos D9 doesn't switch on properly
CZ Eddie said:
Do you get any signs of life on the screen at all? Either Recovery or Download mode? The Galaxy S3 splash screen? Anything at all?
If not, then it's a hard brick and you can get it repaired via a JTAG service (check eBay).
However, if you get ANY signs of life on the screen at all, even if for just a moment, then you might be able to repair things yourself.
Click to expand...
Click to collapse
I bought the Innos D9 and I replaced the rom with the DNS rom and it was working properly till i decided to install the Cloudfone rom .........
after installed the Cloudfone rom I decided to get back the DNS rom and here my phone die ........
now the only thing I see when I switch on my phone is the Cloudfone logo and some stripe .
any help will be really appreciated.
thepinkpanter said:
I bought the Innos D9 and I replaced the rom with the DNS rom and it was working properly till i decided to install the Cloudfone rom .........
after installed the Cloudfone rom I decided to get back the DNS rom and here my phone die ........
now the only thing I see when I switch on my phone is the Cloudfone logo and some stripe .
any help will be really appreciated.
Click to expand...
Click to collapse
You posted in the AT&T, Rogers, Bell, Telus Samsung Galaxy S III section - not sure how much help you will get for that device here.
kbatman74 said:
You posted in the AT&T, Rogers, Bell, Telus Samsung Galaxy S III section - not sure how much help you will get for that device here.
Click to expand...
Click to collapse
big mistake.......you are right ,
thanks alot
CZ Eddie said:
Do you get any signs of life on the screen at all? Either Recovery or Download mode? The Galaxy S3 splash screen? Anything at all?
If not, then it's a hard brick and you can get it repaired via a JTAG service (check eBay).
However, if you get ANY signs of life on the screen at all, even if for just a moment, then you might be able to repair things yourself.
Click to expand...
Click to collapse
thanks great tip will try that to see if mine works!!!!!!
Help me please
hi everyone
I have a problem or a question you just installed cyanogen mod RC1 4.3 on my samsung sgh i747m s3 but display increased consumption up to 70% wanted to know why and also have another question that does not bring the system settings as limiting processes and overclocking put a little less so that is not forced nor brings battery saving I would like to have those two options in cm7 when handling it but this had not anyone know how to put these two options?
I hope your answer!
Thank you!
Thony18 said:
hi everyone
I have a problem or a question you just installed cyanogen mod RC1 4.3 on my samsung sgh i747m s3 but display increased consumption up to 70% wanted to know why and also have another question that does not bring the system settings as limiting processes and overclocking put a little less so that is not forced nor brings battery saving I would like to have those two options in cm7 when handling it but this had not anyone know how to put these two options?
I hope your answer!
Thank you!
Click to expand...
Click to collapse
Your problem has absolutely no impact or solution to the original problem? Create your own thread or use the search function to find a thread with a similar problem you might find a solution or at least people might help you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Bricked?

I rooted the phone with oden and clockwork mod no problem. Installed team win through goo manager. Booted into Team win to flash HD REvolution ROM
Made a backup before flashing. Installed the ROM followed all the promps. Wiped cache and dav. and rebooted system.
Phone wont power on. I can't get into recovery with volume -home -power it's just dead.
Do I have a option or did I brick it somehow?
I have rooted and flashed my Note 2 countless times without issue.
Here is the ROM
http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-SGS3_30.5.zip
Thread
http://forum.xda-developers.com/showthread.php?t=1797334
Care to link the thread for the ROM you flashed I have never heard of it.
Sent from my SPH-L710 using Tapatalk 2
CZuber said:
I rooted the phone with oden and clockwork mod no problem. Installed team win through goo manager. Booted into Team win to flash HD REvolution ROM
Made a backup before flashing. Installed the ROM followed all the promps. Wiped cache and dav. and rebooted system.
Phone wont power on. I can't get into recovery with volume -home -power it's just dead.
Do I have a option or did I brick it somehow?
I have rooted and flashed my Note 2 countless times without issue.
Here is the ROM
http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-SGS3_30.5.zip
Click to expand...
Click to collapse
Please tell me that you weren't flashing this International Rom, from over in the International Section... Or please tell me that you actually have the international version of the phone, and not the Sprint version.
Otherwise, you're hard bricked. The only two solutions you have are to do an insurance return (only if you have Sprint TFE, and even then, some on XDA frown upon using it for hard-bricking your phone), or to do a JTAG repair.
The first rule of flashing is: Read as much as you can prior to flashing, including the stickies!
The second rule of flashing is: Re-read everything you just read and make sure you understand it before flashing anything.
Third
Nevermind found it. You flashed a ROM for the International S3 and bricked your phone. Read one of the other hundred threads were people have done this here. Go buy a Jtag.
Yup its hard bricked there is nothing you can do and no a jig won't work it needs to be Jtagged I heard these guys work wonders mobiletechvideos.com
Sent from my SPH-L710 using xda app-developers app
60.00 lesson learned. I just googled best GS3 Roms got a link and went to the Sprint version. never realized it was a international version. It was my son-in laws phone he took the news pretty well.
CZuber said:
60.00 lesson learned. I just googled best GS3 Roms got a link and went to the Sprint version. never realized it was a international version. It was my son-in laws phone he took the news pretty well.
Click to expand...
Click to collapse
Yeah, unfortunately it's a hard lesson. Back when I first got my S3 (about a month after they came out in the US), I came really close to flashing CM10 for the international phone. The only reason I didn't is because I couldn't find too much information on it and decided to wait a little. I'm glad I did, because shortly after I found that XDA have the Sprint forum. If I hadn't found out on here that international Roms brick our phones, I might've lost out on $150 (TEP deductible).
It's understandable, and now that you're here, you can find tons of great Roms for your son-in-law. Lots of really cool features throughout this forum.
Yeah you are lucky it can be jtagged. Just learn to be sure the ROM is labeled for your model of the phone which is sph-l710 or d2spr.
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png
Odexed Blue by Strong Steve + Ktoonz w/ Team Kernelizers tweaks

Categories

Resources