Database Users

Help needed: New User

I just bought my Epic 4G a few days ago and quickly discovered the existence of rooting and custom ROMS. Needless to say I took the plunge the other day.
I attempted to install the Epic Experience Froyo yesterday but it doesn't seem to load up properly.
Seemed simple enough. I boot into clockwork, I cleared data/factory cache, cache partition, and davnik cache three times each. I installed the ROM from my SD card, install says it's successful, so I hit the reboot.
After this I expect my new rom to load up but all that happens is the samsung logo comes up for about a minute, phone reboots again and goes into the factory Android system recovery utility.
Any ideas? Please help, my phone is inoperable at the moment.
-Dennis

Sounds like kernel. Dl a costume kernel and flash it thru cwm.
Sent from my SPH-D700 using Tapatalk

I'll have to apologize ahead of time because I'm completely new to rooting.
Which kernel should I use (a link to one with instructions would be helpful), and how do I get it on my SD card if it isn't booting up? (my pc doesn't have an SD card reader)

Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209

So, flash Odin/DK17 and then flash Epic Experience over this?

Ya also did you first do the one click root method to make sure you are definitely rooted? If you press. Volume down + camera button + power when booting and the letters are blue you are NOT rooted. If they are green then you are rooted. Sometimes when you install a rom it might take away your root so you might try doing it in the order of this:
1. Flash back to stock 2.1
2. Do theone click root method
3. Flash DK17 modem through odin
4. Install Epic Exprience

hgvidal said:
Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209
Click to expand...
Click to collapse
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?

idontwanttostudy said:
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?
Click to expand...
Click to collapse
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.

hgvidal said:
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.
Click to expand...
Click to collapse
I just did it today with the newest froyo version out by chance would it come with them? If not where can i get them? I cant seem to find the modem to dl

How can i tell by looking in my phone if i have it or not?

idontwanttostudy said:
How can i tell by looking in my phone if i have it or not?
Click to expand...
Click to collapse
Go to settings -> about phone and then check where it says "Baseband version" it should say DK17 in there. If it doesnt follow these instructions to download the files you need. It has step by step directions
http://www.nomie.mobi/how-to-install-dk17-modem-samsung-epic/

I assume this is the rom you flashed:
http://forum.xda-developers.com/showthread.php?t=856715
In the first post it has a link to the instructions to properly flash the rom. You can use those instructions to flash the modem and see if it fixes your problem. You might be better off just flashing everything again. It would mean downloading odin and the files to your pc and flashing them to your phone from your pc. The simplest way to do this is follow this thread
http://forum.xda-developers.com/showthread.php?t=853209
Follow the instructions carefully and when your done you have the new modem, the froyo rom, clockwork recovery, and be rooted.

I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?

idontwanttostudy said:
I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?
Click to expand...
Click to collapse
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App

raylusk said:
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok I finally have it all worked out thanks a lot!

hgvidal said:
1. Flash back to stock 2.1 [through odin]
3. Flash DK17 modem through odin
4. Install Epic Exprience
Click to expand...
Click to collapse
I actually skipped step 2 and everything went fine for me. My laptop was being an asshole and not seeing the phone, so the 1 click root script simply wasn't working.. but then I realized that the DK17 flash via Odin that I got form the epic experience thread included clockworkmod and was pre-rooted and everything so I saw that step as unnecessary.

MOD PLEASE DELETE Thread is of No use

I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it

U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App

afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything

download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing

Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?

distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery

I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?

menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else

sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....

menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk

[Guide] How to root Stock ICS rom without binary count

I'm no longer providing support for this thread due to time constrains with school, thank you for your support and it been nice sharing this method with you all. I may be gone but this method has still been reported as working, but it is possible that the next updates pushed to your phone might break the rooting and this method might not work anymore. But there is no harm in trying, at most you get an error in recovery saying file is invalid.
This method works on the released ICS rom from Germany and I would expect it to work for the rest of the ICS roms due for release..
This method does not increase the binary counter or causes a yellow exclamation mark
Update :
Due to rising numbers of phone being bricked based on rumors and stuff, I strongly suggest NOT trying to use any nandroid backup or restore on this CWM and it is best we keep CWM out of our devices to do major I/O stuff. So far I have never seen anyone bricked their devices on this small rooting/unrooting process but JUST DO NOT MAKE BACKUPS OR RESTORES!
Rooting
Download the Files first and put in your EXTERNAL SD
Reboot to stock recovery. - Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage. - Touch the screen as if you are using the phone to choose the options.
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your EXTERNAL SD
Reboot to recovery.- Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage.- Touch the screen as if you are using the phone to choose the options
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from External SD
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Partial Root
Alright i managed to obtain partial root myself and a fix for the Partial root is quite simple. You can install SuperSU by Chainfire and update the root. would fix the Partial root. Once you install this.. DO NOT USE the Superuser app and DO NOT uninstall the SuperUser app. Use SuperSU from now.
SuperSU - https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
MOD Edit: cwm.zip removed from the attachments, read Entropy512's post.

Thanks, but does this install CWM as well? id like to know so that I can go straight to flashing roms from it

are you sure this works ? can anyone confirm ?

nightfox11 said:
are you sure this works ? can anyone confirm ?
Click to expand...
Click to collapse
Works perfectly. Just rooted stock ICS.

Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium

kvanlier said:
Works perfectly. Just rooted stock ICS.
Click to expand...
Click to collapse
thanks man!

Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.

Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.

akenis said:
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes you will end up with the same result if you take either one of the 2 ways to root
Binary counter is a Samsung measurement of how many times you flashed custom firmwares using PC Odin, and the yellow (not red ) triangle is just a logo to further show that you indeed flashed custom firmware
However, the binary counter will not increase (and therefore no yellow triangle will appear) if you:
1. Flash stock firmware with PC Odin
2. Flash using Mobile Odin app by ChainfireXDA
3. Flash using CWM recovery

I got binary counted to 1 with yellow triangle after flashing ics stock from alba.can i use this method to erase counter and triangle?
Sent from my GT-N7000 using Tapatalk 2

So this gives cwm too looks easy
Sent from my GT-N7000 using Tapatalk 2

Drat?
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?

victorator said:
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Click to expand...
Click to collapse
LordManhattan said:
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
Click to expand...
Click to collapse
Not many ways to have a drastic difference from the method but hey it works well.
p51d007 said:
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
Click to expand...
Click to collapse
This method works as long as you are on Stock ICS.. Can't really go wrong really.

so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!

how come i only got partial root? i cannot paste into system

deathst said:
This method works as long as you are on Stock ICS.. Can't really go wrong really.
Click to expand...
Click to collapse
You are right, finally got my root back ICS, after the 2.3.6 update, been a while, now I have to remember how to use the freeze program, LBE security etc...all over again LOL. THANKS!

elijahtan said:
how come i only got partial root? i cannot paste into system
Click to expand...
Click to collapse
Try rooting again.. Are you sure your file manager app was given permission? Cause this thing is practically fool proof.
nandihno said:
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
Click to expand...
Click to collapse
Glad it works for you Yes I wonder why is not many people taking notice.. :S

...and i thought I was screwed
THANKS MAN. works perfect. much faster than having to redownload the odex vrs

Worked perfectly thanks !
Sent from my HTC One X using xda premium

hmmm.... didn't work for me. CWM looks for update.zip so i renamed it as such. installed and rebooted to CWMR, no touch menu. same old blue colored menu. install su-binary, stuck at unmounting /system = not rooted.

Unable to flash back to stock! Help please?

So, I'm trying to flash back to stock, (either GB or ICS, at this point it doesn't really matter), and PC Odin fails to flash every time it tries to write the factoryfs.img
The only way I can get myself back to a working device is if I do a battery pull, go back into download mode, re-flash CWM and do a recovery back into CM9.
I have tried mobile Odin as well, and again, the flash fails when it reaches factoryfs.img. Are my partitions all screwed up? If so, how can i fix that?
Thoughts? Help? Thanks!

What rom were you on?

Jade Eyed Wolf said:
So, I'm trying to flash back to stock, (either GB or ICS, at this point it doesn't really matter), and PC Odin fails to flash every time it tries to write the factoryfs.img
The only way I can get myself back to a working device is if I do a battery pull, go back into download mode, re-flash CWM and do a recovery back into CM9.
I have tried mobile Odin as well, and again, the flash fails when it reaches factoryfs.img. Are my partitions all screwed up? If so, how can i fix that?
Thoughts? Help? Thanks!
Click to expand...
Click to collapse
You may have a partial brick then same as per this thread
I hope I am wrong and you solve your problem ASAP without any damage
Best of luck

Note_E said:
What rom were you on?
Click to expand...
Click to collapse
IMILKA's CM9 nightly.

Jade Eyed Wolf said:
IMILKA's CM9 nightly.
Click to expand...
Click to collapse
Well there is your problem. Has nothing to do with lpy like the fear mongers blindly think. Toss another one due to CM9...

And like I mention above, it's really weird, I can CWM and still use my device just fine, but if I want to flash new firmware, it freaks out. All I can do is re-flash Chainfire's CWM recovery and restore back to where I was...

Note_E said:
Well there is your problem. Has nothing to do with lpy like the fear mongers blindly think. Toss another one due to CM9...
Click to expand...
Click to collapse
Yeah, I didn't think it had anything to do with LPY, because I still had the same issue when trying to go back to KKA.

Jade Eyed Wolf said:
And like I mention above, it's really weird, I can CWM and still use my device just fine, but if I want to flash new firmware, it freaks out. All I can do is re-flash Chainfire's CWM recovery and restore back to where I was...
Click to expand...
Click to collapse
Beginning of emmc corruption. Not fried just yet. Some recover with pit file then flashing stock gb
Good luck to you bro

Note_E said:
Beginning of emmc corruption. Not fried just yet. Some recover with pit file then flashing stock gb
Click to expand...
Click to collapse
See, that's what I was thinking too... Where can I get the correct .pit file though? I have stock KKA already downloaded; that's what I've been using for a while now for any time I have had to flash back to GB stock for whatever reason.

I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...

Jade Eyed Wolf said:
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Click to expand...
Click to collapse
Looking now. I one you need is around here somewhere

Jade Eyed Wolf said:
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Click to expand...
Click to collapse
Hope this helps

Princeomi said:
Hope this helps
Click to expand...
Click to collapse
I'll give that a try. Thanks!

Just foud one in another thread http://forum.xda-developers.com/showpost.php?p=26009909&postcount=22

I was going to flash stock LC1 via pc odin cos I'm currently on LPY and I'd like to go back to GB. And I think I should ask before flashing that will it work and should I do something else than just hit lc1 in pda and flash?
Sent from my GT-N7000 using xda premium

Princeomi said:
Hope this helps
Click to expand...
Click to collapse
Sadly, those files are packaged in .7zip format. I'm at work right now, and I don't have the admin rights to install 7 zip just to extract it. Can you re-pack and post here in a regular .zip file please?

Jade Eyed Wolf said:
Sadly, those files are packaged in .7zip format. I'm at work right now, and I don't have the admin rights to install 7 zip just to extract it. Can you re-pack and post here in a regular .zip file please?
Click to expand...
Click to collapse
Here it comes

cs_allu said:
I was going to flash stock LC1 via pc odin cos I'm currently on LPY and I'd like to go back to GB. And I think I should ask before flashing that will it work and should I do something else than just hit lc1 in pda and flash?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just flash it, if its a 3 file package put all the 3 files in their respective place, if its one file, put it in pda and flash and also make sure Kies is not running in the background

Well, at least this time the stock flash worked insofar as it completed. However, when the device reset, it went ahead saying "Installing packages" and such, and then it error'ed out saying something like there was invalid argument and it couldn't do something, then I was landed back at the stock recovery. I selected to reboot the system, and now I'm stuck at the Samsung boot animation; just keeps running indefinitely... What now?

Jade Eyed Wolf said:
Well, at least this time the stock flash worked insofar as it completed. However, when the device reset, it went ahead saying "Installing packages" and such, and then it error'ed out saying something like there was invalid argument and it couldn't do something, then I was landed back at the stock recovery. I selected to reboot the system, and now I'm stuck at the Samsung boot animation; just keeps running indefinitely... What now?
Click to expand...
Click to collapse
Hold power button and try to keep rebooting.

[Q] S4 Bootloop, Can enter download but not recovery

Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?

What happens if you put it on download mode and then cancel with vol down

It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.

And if you pull the battery and put it back in does it try to boot?

What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!

megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?

"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.

megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA

jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.

megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.

megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.

Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems