Develop Bugs

Note 2 stuck on bootscreen - Need help please :(

Hello,
I have a very strange problem with my Note 2.... Yesterday i checked mails on my Note 2 when it suddenly shut down and rebooted.
First i didnt think it was a big issue but when it was on login screen where i have to enter my PIN i just touched the screen and it shut down again. Same thing happened again after that. Now it doesnt even boot up anymore... It just stays on Samsung bootscreen all the time. I can get into Download mode but not into recovery for some reason. I had no custom rom or anything else installed on my device. It was completely Stock.
I already tried flashing the firmware again via Odin but without any success....
Now i don't know what to do anymore and hope one of you guys can help me get back into my phone as i don't want to lose the data on it
Thank you in advance
Best regards
Limital

limital said:
Hello,
I have a very strange problem with my Note 2.... Yesterday i checked mails on my Note 2 when it suddenly shut down and rebooted.
First i didnt think it was a big issue but when it was on login screen where i have to enter my PIN i just touched the screen and it shut down again. Same thing happened again after that. Now it doesnt even boot up anymore... It just stays on Samsung bootscreen all the time. I can get into Download mode but not into recovery for some reason. I had no custom rom or anything else installed on my device. It was completely Stock.
I already tried flashing the firmware again via Odin but without any success....
Now i don't know what to do anymore and hope one of you guys can help me get back into my phone as i don't want to lose the data on it
Thank you in advance
Best regards
Limital
Click to expand...
Click to collapse
Try doing a data/factory reset and wipe cache in recovery, you`ll loose the data though. But it is the only way imo.

gee2012 said:
Try doing a data/factory reset and wipe cache in recovery, you`ll loose the data though. But it is the only way imo.
Click to expand...
Click to collapse
Problem is.... im not getting into recovery, it's stuck on Samsung Galaxy Note 2 bootscreen when i do the recovery button combination :crying:

limital said:
Problem is.... im not getting into recovery, it's stuck on Samsung Galaxy Note 2 bootscreen when i do the recovery button combination :crying:
Click to expand...
Click to collapse
Remove and reinsert the battery after 15 seconds and try again.

are you able to get into downloading mode ?
Sent from my GT-N7000 using xda premium

gee2012 said:
Remove and reinsert the battery after 15 seconds and try again.
Click to expand...
Click to collapse
Tried that a hundred times but it still wont go into recovery and it wont boot android. Just stays on Samsung Note 2 bootscreen.
Only thing working is download modus but as stated above flashing firmware anew didn't help....

limital said:
Tried that a hundred times but it still wont go into recovery and it wont boot android. Just stays on Samsung Note 2 bootscreen.
Only thing working is download modus but as stated above flashing firmware anew didn't help....
Click to expand...
Click to collapse
Then you have to take it to a samsung service center or the store for repair mate.

Anyone else with an Idea? What i also think is strange is that it says in Download mode that i downloaded 5 Custom Roms and my Current Binary and System Status are Custom???? I just installed the official firmware from SamMobile again -.-

Noone able to help me? I'm going insane at the moment cause nothing works.... Even when i plug in the usb cable the phone boots to the Galaxy Note 2 screen and nothing else happens.... In download modus it says i'm on a custom rom what i never installed to begin with....i only installed Stock Rom.... Please help what should i do T_T

So now i flashed the Rescue Rom but it did not change anything. Odin completed the flashing without errors though nothing changed. Also tried flashing Stock Firmware again but the status in download mode still shows custom system and binary.... Could it be that Odin is not flashing correctly though it is not giving me any errors?
I'm really desperate at the moment -.-

My galaxy s1 was bricked at one stage. I took the battery out and left it for am hour then I got it to boot into download mode. Are you putting the right rom on it? Like a whole factory rom?
Sent from my GT-N7105 using xda app-developers app

Yes already tried Stock Rom and also the rescue rom.... nothing changed

Can you flash CWM onto it? Then turn it off., hold down volume up, home and then power Tool you see Samsung logo?
Sent from my GT-N7105 using xda app-developers app

Already tried root with CWM but it won't go into recovery either. I also tried flashing the rescue rom with Pit-File but it does not go further than bootscreen. At the moment i really don't know whats wrong with the phone and i'm a bit desperate right now....
Isn't there anybody who's able to help me with this, please?
regards limital

Try to closely read this http://forum.xda-developers.com/showthread.php?t=1923956.
Then try to use Note 2 Toolkit.
Does it work?
Among other features, this one (as stated on their thread):
Flash Stock Boot Image back to your phone
Click to expand...
Click to collapse

Go to download mode & flash CWM.Remove battery & reinsert it. Go to cwm mode now & wipe dalvik, cache & data reset. Flash a new firmware thru pc odin. It will start. I did it. Take a chance.
Sent from my GT-N7100 using xda premium

Happened to me today.i cant get into twrp recovery,cant boot normally.
I pc odin flash cwm recovery and its work again.good luck to you hope u can make it.

stuck on bootscreen. Please help me
Hi guys. I just recently root my note 2 but not flashing custom rom. Then i try to mess around with the rom toolbox apps and changed the font. After reboot, i just stuck at the bootscreen.
Please help

maheshhtc said:
Go to download mode & flash CWM.Remove battery & reinsert it. Go to cwm mode now & wipe dalvik, cache & data reset. Flash a new firmware thru pc odin. It will start. I did it. Take a chance.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Nice that it worked for you Just tried it but it does not work for me... I'm still stuck at bootscreen

Boot screen stuck
Hi TS,
U need to first let us know which variant of the note 2 u are using.
is u want to solve the bootloop issue,u need to follow these step as posted by someone here:
1. flash CWM using odin,then boot into CWM(power+vol up+that centre button) then wipe dalvik> cache partition > then data reset
2.DL sammy's official firmware for your note variant (7105 or 7100 or whatever)
3.flash sammy's firmware thru odin
4.let phone boot into android
then do whatever you need to do.
I had the same prob at you did,followed that guy's advice and not everything is back to factory and i can send it in for warranty.

Can't get pass bootscreen Note 2

situation...
-flashed the phone using odin pc
-installed clockwork recovery using rom manager pro app on phone
-flashed 'cleanrom' onto phone didn't like it so flash another rom 'jedi x'
-didn't clean/wipe data before flashing it
-flashed 'jedi x' then the phone restarted
-didn't finish restart, stuck in bootloop...
tried to reflash CWM6 onto my phone using download mode and pc odin didn't get pass bootscreen 'samsung' logo
tried to enter recovery mode by holding vol up + home + power... can't get access to recovery mode....
desperately need help... please help!!!

try wiping... 2 different roms won't pay nice if you don't wipe
Sent from my SPH-L900 using xda app-developers app

I'm actually in the exact same situation. I was simply transferring music to my phone when it went into this boot loop. I've tried using ODIN to flash every possible ROM I've been able to find.
Desperately in need of help.
How exactly do I perform a "wipe"?

1. Can you guys get into Download and or Recovery mode?
2. If recovery is available, did you back up? If so, restore or flash back to original Rom.
3. If you can get into Download mode, flash back to a stock Rom, and start fresh.
Might sound obvious, just trying to help. I've learned that often I thought the phone was "done", but after refusing to give up on it, it came back to life...
Just keep trying , sounds recoverable for both.
---------- Post added at 10:07 PM ---------- Previous post was at 10:01 PM ----------
QuantumPSI said:
I'm actually in the exact same situation. I was simply transferring music to my phone when it went into this boot loop. I've tried using ODIN to flash every possible ROM I've been able to find.
Desperately in need of help.
How exactly do I perform a "wipe"?
Click to expand...
Click to collapse
You can wipe by getting into recovery. Wipe Data, cache, dalvik cache.

I can only get into download mode and I've tried to flash to stock ROM SEVERAL times now to no avail.
I've noticed that the binary counter isn't going up after each attempt though...

QuantumPSI said:
I can only get into download mode and I've tried to flash to stock ROM SEVERAL times now to no avail.
I've noticed that the binary counter isn't going up after each attempt though...
Click to expand...
Click to collapse
So, does odin say- succeeded or failed or do nothing when you flash?

Says succeeded every single time.

QuantumPSI said:
Says succeeded every single time.
Click to expand...
Click to collapse
Were you on LK8 or LJC ? No recovery?

LJC, and no, no recovery

QuantumPSI said:
LJC, and no, no recovery
Click to expand...
Click to collapse
Not even stock recovery? - power + home key + vol up ?

never gets to that menu... just reboots

QuantumPSI said:
never gets to that menu... just reboots
Click to expand...
Click to collapse
Well, all I can say is keep trying or a hammer. It's bound to work once... Sorry but I dont know what else to tell ya.
Good luck with it!

Hmm, there really doesn't seem to be a solution to this. Any possible way to "fastboot" it?

Anyone know where I can find a PIT file?

[Q] How to resolve this bootloop

Hi, I have a problem on my Galaxy GIO GT-S5660.
After turning off my phone, this has gone in bootloop. I've tried to search solutions on the forum, but no one has worked.
I can't go into recovery mode, just into Downloading mode and Emergency Downloading mode. When I try to flash it with a stock rom with Odin, it works until the reboot: when the phone is going to reboot, it doesn't start again. Odin takes his 5 minutes and say "PASS", but the phone is in the same bootloop and I can't use the Recovery mode.
I tried to flash the rom with Odin just using One Package option and either putting 4 packages.
Any idea?
Thanks!
P.S.: Do you know what is "Parameter Clear", "PDA format", "MD5 RAM Check" and "Phone Boot Udpate" under the "Debug ONLY" menu? I use Odin Multi Downloader v4.42.

what did you do? rom manager?
cuz not booting and corrupt recovery cant happen out of nothing, and it are complications of using rom manager on the wrong way.
Sent from my GT-S5660 using xda app-developers app

BOOTLOOP
After updating, from samsumg, my android doesn't start and i cann't use it. Try everthing, any ideias?

It sounds like we have the same problem.
My phone won't boot normally (I just get a black screen that flashes every few seconds) and I can't get into recovery mode, only download mode. Tried flashing with Odin and it didn't seem to change anything. I don't know what else to do.

R: [Q] How to resolve this bootloop
voetbalremco said:
what did you do? rom manager?
cuz not booting and corrupt recovery cant happen out of nothing, and it are complications of using rom manager on the wrong way.
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Accidentally used Mobile Odin on the wrong phone. After the use of that application the phone continue to work properly, I had that problem After rebooting.
angus.mcinnes said:
It sounds like we have the same problem.
My phone won't boot normally (I just get a black screen that flashes every few seconds) and I can't get into recovery mode, only download mode. Tried flashing with Odin and it didn't seem to change anything. I don't know what else to do.
Click to expand...
Click to collapse
I have the same black flashing screen when my Gio is charging, but I have the Samsung logo flashing every few seconds when I try to switch on the phone. What did you do on yours? Rom Manager or what?

Vharcan said:
What did you do on yours? Rom Manager or what?
Click to expand...
Click to collapse
It might have been that I tried to read /dev/stl5 (EFS partition) and that corrupted it. Or it might have been that I tried to flash it using heimdall (which I later discovered doesn't work on Gio). That didn't seem to do anything though, so I'm not sure what actually bricked it.

R: [Q] How to resolve this bootloop
angus.mcinnes said:
It might have been that I tried to read /dev/stl5 (EFS partition) and that corrupted it. Or it might have been that I tried to flash it using heimdall (which I later discovered doesn't work on Gio). That didn't seem to do anything though, so I'm not sure what actually bricked it.
Click to expand...
Click to collapse
I would try to use PDA format under Debug Only menu in Odin 4.42, if I only knew what it does. Or maybe use Boot Update, under Debug menu... do you know any official manual of Odin and his Debug options?

Vharcan said:
I would try to use PDA format under Debug Only menu in Odin 4.42, if I only knew what it does. Or maybe use Boot Update, under Debug menu... do you know any official manual of Odin and his Debug options?
Click to expand...
Click to collapse
I tried those. PDA format makes Odin crash. Boot update doesn't help.

R: [Q] How to resolve this bootloop
angus.mcinnes said:
I tried those. PDA format makes Odin crash. Boot update doesn't help.
Click to expand...
Click to collapse
Same crash bere with PDA format, but I tried Odin 4.42. You too?

Can you guys still boot into recovery? If not, try flashing recovery via Odin. Once in recovery, factory reset your device, wipe system, wipe dalvik, wipe everything. Then try once again with Odin to flash your stock ROM - try a one package file (includes everything).

Codename13 said:
Can you guys still boot into recovery? If not, try flashing recovery via Odin. Once in recovery, factory reset your device, wipe system, wipe dalvik, wipe everything. Then try once again with Odin to flash your stock ROM - try a one package file (includes everything).
Click to expand...
Click to collapse
I can't get into recovery. If I boot while holding [home], the screen just blinks every few seconds, the same as if I boot without holding anything. I have tried flashing CWM recovery or stock ROM with Odin; it doesn't seem to change anything.

R: [Q] How to resolve this bootloop
angus.mcinnes said:
I can't get into recovery. If I boot while holding [home], the screen just blinks every few seconds, the same as if I boot without holding anything. I have tried flashing CWM recovery or stock ROM with Odin; it doesn't seem to change anything.
Click to expand...
Click to collapse
The same here. I tried to flash a cwm recovery, a stock recovery, anche extracted-from-one-package-and-hand-build recovery, but nothing changes. Only Samsung-logo bootloop.

Vharcan said:
The same here. I tried to flash a cwm recovery, a stock recovery, anche extracted-from-one-package-and-hand-build recovery, but nothing changes. Only Samsung-logo bootloop.
Click to expand...
Click to collapse
Any news on this? iam with the exact same problem.
Did you got it?

have you tried to flash cwm whit odin? you don't need a rom to boot just flash a recovery twrp/cwm and wipe everything or you can try this http://forum.xda-developers.com/showthread.php?t=1153310

It's happening the same form me... I never used Rom Manager WTH!!! I flashed a lot of times on my samsung galaxy ace stock roms, and never happened this... dunno what to do but this is so strange... can go in download but flash when I flash any stock, stays the same "flash" bootloop, samsung logo only 1s and disappear 1s and the same... nothing...

[Q] stuck at "samsung" on boot

I'm following the post http://forum.xda-developers.com/showthread.php?t=1739426&nocache=1 (for the second or third time) to flash the stock rooted rom onto my att s3. I've done this before a few times and never had an issue.
I'm following them to the letter tonight and everything goes ok (at least ODIN says its ok...) but the phone won't get past the SAMSUNG logo on the restart. ODIN finishes, I see the green Android guy and a progress bar, then I think it reboots again, I get the samsung/at&t logo with sound, then it just stays on the SAMSUNG screen. I gave it time, up to 20 minutes, to finish anything it was doing.
Any help would be appreciated.
(Why am I doing this? I flashed CM 10.1 and somehow LTE didn't work, so I went to CWM and flashed my backup and I couldn't get any phone/data to work. So thinking something got fouled up I decided to just re-flash from the above post to get what I had, which was working.)

zshguru said:
I'm following the post http://forum.xda-developers.com/showthread.php?t=1739426&nocache=1 (for the second or third time) to flash the stock rooted rom onto my att s3. I've done this before a few times and never had an issue.
I'm following them to the letter tonight and everything goes ok (at least ODIN says its ok...) but the phone won't get past the SAMSUNG logo on the restart. ODIN finishes, I see the green Android guy and a progress bar, then I think it reboots again, I get the samsung/at&t logo with sound, then it just stays on the SAMSUNG screen. I gave it time, up to 20 minutes, to finish anything it was doing.
Any help would be appreciated.
(Why am I doing this? I flashed CM 10.1 and somehow LTE didn't work, so I went to CWM and flashed my backup and I couldn't get any phone/data to work. So thinking something got fouled up I decided to just re-flash from the above post to get what I had, which was working.)
Click to expand...
Click to collapse
Enter recovery and wipe data/factory reset. You have things from CM10 lingering and this wipe will fix them.

BCSC said:
Enter recovery and wipe data/factory reset. You have things from CM10 lingering and this wipe will fix them.
Click to expand...
Click to collapse
I can't do anything. It won't boot past the SAMSUNG screen. I don't have CWM or anything

Manually boot into recovery, then do a factory reset

mrhaley30705 said:
Manually boot into recovery, then do a factory reset
Click to expand...
Click to collapse
When I try to do that, the screen just goes black.
I tried flashing CWM using heimdall (http://forum.xda-developers.com/showthread.php?t=1728981) and got this error ... ERROR: Partition "recovery" does not exist in the specified PIT.

zshguru said:
I can't do anything. It won't boot past the SAMSUNG screen. I don't have CWM or anything
Click to expand...
Click to collapse
you wont have CWM if you have stocked via Odin, but you will have 3e recovery with same option. Use same 3 button combo to get recovery

Suggestion
I sort of had the same issue except I didn't have any issues with recovery. I flashed 4.1.1 via ODIN and then got stuck at the Samsung logo. ODIN said passed so I did a battery pull and booted into stock recovery (holding volume key up + home button (keeping both held until I was in recovery) and hit the power button) and I had to do a factory reset and wipe cache and then reboot. Could maybe try flashing via ODIN again and giving that a shot if you haven't yet.

ToXicWinter said:
I sort of had the same issue except I didn't have any issues with recovery. I flashed 4.1.1 via ODIN and then got stuck at the Samsung logo. ODIN said passed so I did a battery pull and booted into stock recovery (holding volume key up + home button (keeping both held until I was in recovery) and hit the power button) and I had to do a factory reset and wipe cache and then reboot. Could maybe try flashing via ODIN again and giving that a shot if you haven't yet.
Click to expand...
Click to collapse
Yeah I will try to flash again via ODIN and will try the recovery thing.

zshguru said:
Yeah I will try to flash again via ODIN and will try the recovery thing.
Click to expand...
Click to collapse
Finally, got to recovery and did a factory reset/wipe and cleared the cache. Rebooted and still stuck on sammy screen. Trying to reflash stock via odin.

zshguru said:
Finally, got to recovery and did a factory reset/wipe and cleared the cache. Rebooted and still stuck on sammy screen. Trying to reflash stock via odin.
Click to expand...
Click to collapse
Woohoo --- it worked! The damn thing is back lol.

Good deal bro. I know when that happened to me last week I had a mini heart attack lol.
Sent from my SAMSUNG-SGH-I747 using xda premium

ToXicWinter said:
Good deal bro. I know when that happened to me last week I had a mini heart attack lol.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
triangled-away, back to stock. now i can take my s3 back to at&t for warranty replacement (data stopped working)
thank you every who assisted me. i really appreciate it.

[Q] Phone bricked, no ODIN access! E: Unable to mount '/data'

Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster

Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2

elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster

I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.

Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC

Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.

lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash

elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster

Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.

lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!

Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD

elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster

I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.

coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.

Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium

Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.