Related
Help...
I had a working phone with 3.0 golden eye.
I had installed Hide it Pro and File Hide it.
I was able to use the File Hide it but after reboot, the screen got stock at Samsung S4 Logo screen and I tried to restore and was TWRP says restored but during reboot it will get stock still at the Samsung S4 logo.
Now, I am trying desperately how to even just make it work.
I remember last time I had installed Hide It Pro and it also got my older phone get stock in the same situation and had used a different ROM.
this is the 2nd phone that is stock after installing Hide It Pro.
Any suggestions on how to revive my phone?
I am currently downloading the stock "I337UCUAMDB_I337ATTAMDB_ATT.zip" and will try to Odin it.
I am looking to use the later UCUADML stock rom.
Thank you.
qwer43 said:
Help...
I had a working phone with 3.0 golden eye.
I had installed Hide it Pro and File Hide it.
I was able to use the File Hide it but after reboot, the screen got stock at Samsung S4 Logo screen and I tried to restore and was TWRP says restored but during reboot it will get stock still at the Samsung S4 logo.
Now, I am trying desperately how to even just make it work.
I remember last time I had installed Hide It Pro and it also got my older phone get stock in the same situation and had used a different ROM.
this is the 2nd phone that is stock after installing Hide It Pro.
Any suggestions on how to revive my phone?
I am currently downloading the stock "I337UCUAMDB_I337ATTAMDB_ATT.zip" and will try to Odin it.
I am looking to use the later UCUADML stock rom.
Thank you.
Click to expand...
Click to collapse
Actually have you tried a factory reset yet? I would try that first before Odin.
That will work, make sure after you odin, you do a factory reset, or you will still see the same issue, odin does NOT do a factory reset.
Good luck.
head over to http://www.sammobile.com/firmwares. you'll have to register as a user but they have the MDL firmware you are looking for.
xBeerdroiDx said:
head over to http://www.sammobile.com/firmwares. you'll have to register as a user but they have the MDL firmware you are looking for.
Click to expand...
Click to collapse
I will check this link too. Thanks.
TheAxman said:
Actually have you tried a factory reset yet? I would try that first before Odin.
That will work, make sure after you odin, you do a factory reset, or you will still see the same issue, odin does NOT do a factory reset.
Good luck.
Click to expand...
Click to collapse
You are right. I did a factory reset first, did not work so my last resort was ODIN.
I did ODIN and I was able to see the apps and play with it. after reboot, got stock again at Samsung Galaxy S4 logo.
I wil ODIN again and after reboot in the phone, I will do a factory reset since I believe the phone is non-rooted at this point.
I will post back what happens.
Thanks.
qwer43 said:
You are right. I did a factory reset first, did not work so my last resort was ODIN.
I did ODIN and I was able to see the apps and play with it. after reboot, got stock again at Samsung Galaxy S4 logo.
I wil ODIN again and after reboot in the phone, I will do a factory reset since I believe the phone is non-rooted at this point.
I will post back what happens.
Thanks.
Click to expand...
Click to collapse
It's getting frustrating.
I had ODIN my phone, reboot and factory reset by using the vol up+power+home.
stock was fine.
rooted the phone and installed SHOstock 2.0 by wiping all including format data.
at first reboot, gets stock on the samsung logo...
what else can I do to fix this even if i had already rolled it back to stock/factory reset?
Thank you.
qwer43 said:
It's getting frustrating.
I had ODIN my phone, reboot and factory reset by using the vol up+power+home.
stock was fine.
rooted the phone and installed SHOstock 2.0 by wiping all including format data.
at first reboot, gets stock on the samsung logo...
what else can I do to fix this even if i had already rolled it back to stock/factory reset?
Thank you.
Click to expand...
Click to collapse
Flash the KT att loki kernel and see what happens, it will boot.
TheAxman said:
Flash the KT att loki kernel and see what happens, it will boot.
Click to expand...
Click to collapse
What is the "KT att loki kernel"? I tried searching for these strings "KT att loki kernel" but nothing relevant.
I would appreciate your assistance.
Thank you.
qwer43 said:
What is the "KT att loki kernel"? I tried searching for these strings "KT att loki kernel" but nothing relevant.
I would appreciate your assistance.
Thank you.
Click to expand...
Click to collapse
I have now Goldern 3.0 ROM but after the 1st boot, it is stock again at the logo.
Will the "KT att loki kernel" all ROMs?
Thank you.
here's the link to KT's kernel thread: http://forum.xda-developers.com/showthread.php?t=2292341
there are 2 kernels. download the correct one for your type of firmware (touchwiz or aosp).
cheers
xBeerdroiDx said:
here's the link to KT's kernel thread: http://forum.xda-developers.com/showthread.php?t=2292341
there are 2 kernels. download the correct one for your type of firmware (touchwiz or aosp).
cheers
Click to expand...
Click to collapse
I had downloaded AOSP kernel. I have this ROM "
[ROM]★GOLDENEYE★[ATT&CAN][►XXUBMF8◄][APPS2SD][JB][TW][4.2.2][LOKi'D][July.14.13]"
Flashed it.
While clearing Cache/Dalvik, ok
Fix permission : ok
Reboot. it showed logo then phone turned-off screen, no response...
help.... needed...
You downloaded the aosp kernel and flashed it on a touchwiz (TW) rom. Can you get into recovery mode?
xBeerdroiDx said:
You downloaded the aosp kernel and flashed it on a touchwiz (TW) rom. Can you get into recovery mode?
Click to expand...
Click to collapse
Ooops, my bad. Golden ROM is a Touchwiz?
I will try to recover it and flash the Touchwiz Kernel.
going back to original issue.
AFter I had ODIN my phone and flashed a new ROM, I should not be having these issues(?). right?
qwer43 said:
Ooops, my bad. Golden ROM is a Touchwiz?
I will try to recover it and flash the Touchwiz Kernel.
going back to original issue.
AFter I had ODIN my phone and flashed a new ROM, I should not be having these issues(?). right?
Click to expand...
Click to collapse
I had ODIN it again.
After reset/reboot, since it is connected to my pc the invisible batter in the background appears and does nothing after the ATT logo with sounds came out.
disconnected from pc and tried to reboot. it will only show the logo during power button push, release the power button and the logo disappears and dies.
qwer43 said:
I had ODIN it again.
After reset/reboot, since it is connected to my pc the invisible batter in the background appears and does nothing after the ATT logo with sounds came out.
disconnected from pc and tried to reboot. it will only show the logo during power button push, release the power button and the logo disappears and dies.
Click to expand...
Click to collapse
I tried reboot in recover, power+vol up and home, the phone will show the logo and release power and it dies, does not continue to recovery.
Is there any other way to recover the phone?
Thank you.
qwer43 said:
I tried reboot in recover, power+vol up and home, the phone will show the logo and release power and it dies, does not continue to recovery.
Is there any other way to recover the phone?
Thank you.
Click to expand...
Click to collapse
my bad again...
battery was dead.
now, after ODIN, I am in stock ROM, none rooted.
restarted = ok
power off > start = ok
next rooting steps.
what I can't understand is when flashing a new ROM will start to freeze at start-up... ???
qwer43 said:
my bad again...
battery was dead.
now, after ODIN, I am in stock ROM, none rooted.
restarted = ok
power off > start = ok
next rooting steps.
what I can't understand is when flashing a new ROM will start to freeze at start-up... ???
Click to expand...
Click to collapse
because you must use a kernel for your device...PERIOD! If you do not, you will hang at boot.
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
NidexX said:
Hi!
So I followed Djembeys guide to root my s4 back when ME2/MF2(or smthn in that matter)was the newest firmware avable. But now I wanted to go back to stock and update my phone and as stated in the guide that would be no problem, well OTA didn't work so i did it via Kies. It worked as expected for a while before my phone started freezing and rebooting itself forever, like as soon as i get into the launcher.
Things I've tryed to do:
*Checking in download mode that everything is official, it is, and the phone doesn't seem to reboot while in download mode, should I flash a stock rom, I mean, what if the phone shuts off in the middle of the process?
*Doing a factory data reset via stock recovery, the "android" in recovery falls down and a triangle at his stomach. However the data reset worked, but it didn't solve the problem, still reboots but now when the phone is trying to set itself up.
What can i do guys? You think i can send it back to the store seeing everything is official in download mode?
Click to expand...
Click to collapse
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Which s4 is this? This is the sprint variant. Post it in the appropiate s4 of your carrier. You can try to odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Aww really, i totally missed that this was for sprint:/. I have the NEE version(unbranded GT-I905). Are you sure i can flash stock, what if it would reboot while flashing? It is already stock, just that I have this damn problem with the reboots;(
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
jejb said:
Mine did some of that kind of thing when I first went to MF9 a few days ago. I think the reason I had the problem was because I did a nandroid recovery using a custom recovery (TWRP). I think (but have no proof) that it overwrote some of the MF9 stuff with MDL stuff. So to fix it, I redid everything and recovered my apps and data through Titanium Backup instead. All good now.
Follow the directions I posted yesterday in the following thread to get to unrooted, stock MF9:
http://forum.xda-developers.com/showthread.php?t=2427006
Click to expand...
Click to collapse
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
NidexX said:
It worked fine and your phone didn't reboot in download mode? I've tested to be inside download mode for around 10 min, so i guess it's fine if i flash stock rom.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm now very stable on MF9, rooted, stock rom.
jejb said:
I'm not exactly sure what you're asking, but the phone worked fine once I redid it. Before that, it would have random boots, and then multiple boots like a boot loop. But it never did more than 2 boots before actually coming up. But it would reboot after a while. BlueTooth would not turn on, stuff like that. It just was not right. But the redo with the TiBu restore worked great. I'm not very stable on MF9, rooted, stock rom.
Click to expand...
Click to collapse
nvm dude, seems like it's hardware failure. I tried flashing it with stock MGA firmware and the problem remains, as well as the screen ****ing up just before it is about to reboot. Well, thanks anyway!
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
So I rooted my phone months ago, found a KK ROM I was happy with and never had any issues, until last night.
My battery died. When I went to plug it in and power it on, it went to the Samsung Galaxy Note 3 screen with the pad lock unlocked on it. I then noticed on the top right it said recovery booting. I figured no biggie, I'd let it boot to recovery and then reboot. Well it never got into recovery, and restarted, yielding the same results after a restart. So basically, my phone is on for about 5 seconds, then shuts off and tries again.
I tried to pull the battery and left it out over night. This morning I pushed the recovery button sequence to make sure the power was completely drained then reinserted the battery. As soon as I put the battery in, it starts to boot, shows booting recovery, then loops. I tried plugging in to my PC to see what happened and that didn't help. Is my phone screwed or what should I do to try to fix this?
Can you get into download mode
waco2hot33 said:
Can you get into download mode
Click to expand...
Click to collapse
Yes I can! Wasn't abled to last night but now I can. What version of odin do I need and what firmware do I flash?
instant3 said:
Yes I can! Wasn't abled to last night but now I can. What version of odin do I need and what firmware do I flash?
Click to expand...
Click to collapse
Nc4 firmware and odin 3.09
waco2hot33 said:
Nc4 firmware and odin 3.09
Click to expand...
Click to collapse
After I falsh in ODIN, do I have to reroot, reinstall safestrap, etc?
instant3 said:
After I falsh in ODIN, do I have to reroot, reinstall safestrap, etc?
Click to expand...
Click to collapse
That is correct.
gmskking said:
That is correct.
Click to expand...
Click to collapse
I am thinking I want to try out JasmineROM 2.4 out. Do I need to flash the unified KK firmware in ODIN prior to install? I tried flashing without doing this and it just fails immediately. I see that the unified KK firmware is there so I was just wondering. Also, when I flash that, do I just do it in ODIN in the PDA box, same as I flashed the nc4 firmware yesterday? Thanks for your help, fellow Iowan!
I had this happen recently. I had to go back to a complete stock NC4 stock 4.4.2 and reroot and go from there. I used a newer version of Odin though.