Database Users

[Q] no access to stock recovery

Hi guys,
I recently bought an Ideos X5 that was 2 months in use and it seems like I can't boot into stock recovery with it.
My device is definitely not rooted (Checked it with the app RootChecker). When I got it, I did a factory reset right after in stock recovery. I was able do get there with VOL+, HomeButton and Power. Neither this nor VOL+/VOL- and Power works now. I do not just reboot but boot when the phone is turned off. Android-Version is 2.3.5, Kernel 2.6.35.7, Build-Number ...B522... All I did so far was the factory reset.
Sorry I'm still not used to all this stuff although I read a lot, but seems like the more I read the more I get confused. Maybe it's totally easy but I tried a lot of things and none worked
Thanks a lot.

Try first holding down vol+ then power and then hold both of them until it either gets into recovery or its fully booted, depending if it works or not.
Sent from my U8800 using Tapatalk 2

MrTeflon said:
Hi guys,
I recently bought an Ideos X5 that was 2 months in use and it seems like I can't boot into stock recovery with it.
My device is definitely not rooted (Checked it with the app RootChecker). When I got it, I did a factory reset right after in stock recovery. I was able do get there with VOL+, HomeButton and Power. Neither this nor VOL+/VOL- and Power works now. I do not just reboot but boot when the phone is turned off. Android-Version is 2.3.5, Kernel 2.6.35.7, Build-Number ...B522... All I did so far was the factory reset.
Sorry I'm still not used to all this stuff although I read a lot, but seems like the more I read the more I get confused. Maybe it's totally easy but I tried a lot of things and none worked
Thanks a lot.
Click to expand...
Click to collapse
Should locked bootloader cause this? Because 522 has a locked bootloader. Atleast try to unlock the bootloader. There was a tutorial about this, search the forum
Sent from my U8800

I already found this tutorial,
http://forum.xda-developers.com/showthread.php?t=1457490
but the phone has to be rooted to do that or you have to get to stock recovery, so it didn't work obv.
I tried VOL+/Power, didn't work as well.
Thanks though. Any more ideas?

MrTeflon said:
I already found this tutorial,
http://forum.xda-developers.com/showthread.php?t=1457490
but the phone has to be rooted to do that or you have to get to stock recovery, so it didn't work obv.
I tried VOL+/Power, didn't work as well.
Thanks though. Any more ideas?
Click to expand...
Click to collapse
By did not work, do you mean it booted Android instead? If you don't want to root your device, you should reflash the firmware, but back up your things first.

Yes it booted normally. Maybe I'm gonna do that... Weird thing is that I did nothing but a factory reset and 3 or 4 apps like games and whatsapp.

aaaahhhh I got it. Had to untick "fast boot" in settings. Didn't really know that this is activated... anyway, thanks.

MrTeflon said:
aaaahhhh I got it. Had to untick "fast boot" in settings. Didn't really know that this is activated... anyway, thanks.
Click to expand...
Click to collapse
Looo
Sent from my U8800pro using xda premium

AT&T Galaxy S4 Wont Boot into Recovery

I have a client's Atnt galaxy s4 that will not boot up normally and will not boot into recovery also.
when i try to boot into recovery i get the blue lettering in the top left and it just sits there i have let it sit for sometime like that with no change.
this is not my first go around with flashing android devices so please even give me Dev only options if that is what you think will fix it. i feel bad because he just bought this phone 2 weeks ago and cant use it. not sure what the other guy that tried to root it did and neither does he so i am shooting in the dark so any help would be great.
I have tried flashing the stock Odin package with no luck.
Also tried Kies Firmware upgrade with no luck
Most of the custom recovery for this phone from what i read are not flashed threw odin anymore, but if i am wrong please link me and i will give it a shot.
Dose anyone have any ideas someone told me to use the .PIT file and re-partition the device and reflash the stock odin package. but i have had no luck locating the .pit file for the I337 galaxy S4 could anyone grab it from there phone and upload it for me or any ideas on how i could possibly fix this issue.
Thanks in advance

Since you already tried ODIN, why don't you try KIES.

I tried that allrdy just forgot to add it to the list updated first post

Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app

C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
ok i will have him give it a try
and yes it goes into downloading mode with no issues at all.

if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.

C13v3r0n3 said:
if the os isnt hosed just download goomanager and install the recovery then download a touchwiz rom that has an extended reboot menu, you can then just boot into recovery from the OS.
Click to expand...
Click to collapse
The OS wont boot that is why we are having such a issue cause we have to get into the recovery to fix the phone
thanks thou

If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app

In addition to letting go of the power button after the vibrate, here are a couple of other things that appear to have worked for other forum members. I didn't discover any of these fixes, I just did a lot of reading and saw where others have had similar problems and found ways to solve them. That is what makes the XDA community great:
Uppercuticus said:
I've had this happen to me several times while playing around with flashing. Basically (without fail in my experience), hold power+volume up+home as you'd normally do until you see the booting recovery message and let go. It will do one of two things - boot into recovery- or - restart and vibrate-. If it restarts and vibrates, immediately hold power+volume up+home until the booting recovery message pops up again and let go. It should then boot into recovery and you shouldn't have trouble in subsequent attempts.
It took me a while to figure this out and I actually thought I had permanently bricked my phone as the phone wouldn't boot and I couldn't get into recovery. Hope this helps.
Click to expand...
Click to collapse
RiNo808 said:
Those trying to boot into recovery mode, dl quick reboot from the play store. That's what I use and it works great.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse

Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.

C13v3r0n3 said:
If you can get into download mode and odin it should wipe everything, it should work. Maybr its hardware?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
After using ODIN, make sure to do a software (factory reset) to get rid of any data and settings that stayed behind. The firmware packages that we have for Odin, do not wipe everything on their own.

C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanks - was having the same problem. At last somebody explains it properly. It worked.
(Why on earth is the script on the stock recovery screen so small. You need a microscope to read it. I am going to install CWM right away....)
Cheers LJ

S4 on veriozon only boots into download mood
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!

Yankeetim92 said:
Im having the same problem. I can ONLY get into download mood! Everytime I go and try to reboot all it does is vibrates. I was installing a rom before and it was installed fine then it says I lost my root and turned off. Now i can't turn my phone back on. I try to the NAND erase all but that does not work. Is my phone bricked? I have Verizon BTW. Could some body please help me ASAP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=2316

any luck? im having the same problem after enabling the t-mobile aws bands on my i337. i could only get into odin mode, recovery boot sits there on end and i have no access to the phone settings. ive tried the odin with stock firmware but nothing.

xBeerdroiDx said:
http://forum.xda-developers.com/forumdisplay.php?f=2316
Click to expand...
Click to collapse
you are not playing fair sir...but a good one.

TheAxman said:
you are not playing fair sir...but a good one.
Click to expand...
Click to collapse
My unrooted s4 phone gets stuck with the blue colour legend Recovery booting with any mentioned method. I am unable to enter safe mode, any ideas? been surfing google for 6hrs with no proper answer. Thanks!!

C13v3r0n3 said:
Copied this from another thread, guy was having same issue.
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
Phone goes into download mode ok?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Thanx bro, This is solve my problem.

Having allmost the same problem with my S4...
http://forum.xda-developers.com/showthread.php?t=2498285

continuation of SGH_1337 will not boot into recovery
norml said:
Just flash a different custom recovery tar in odin. If ur using CWM, then flash TWRP, or vice versa.
Click to expand...
Click to collapse
here are all the details;
Rooted ATT Galaxy S4 MK2 with Busybox. all went well until I tried to flash and boot into recovery. Installed ClockworkMod Recovery, tried to reboot into recovery...permission error. Installed Team Win Recovery, same problem.
investigated... Superuser.apk for some reason is NOT present in app directory. hmm. checked for root, have root.
installed ClockworkMod Superuser from play store... asks to update superuser... fails with signature error.
There seems to be no way to flash this phone. I have the original backup I made with ClockworkMod but restore fails with signature error.
The phone works fine, has root but I am concerned I will not be able to update to 4.4 when it's available. I am also NOT able to flash any alternative ROM. frustrating.
I see there are relatives to this issue all over xda but as far as I can tell after a weekend of trying is there's NO WAY to boot into recovery with write permissions being allowed.

[Q] Factory Reset from Fastboot

Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks

mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
I am in the same predicament. I hope there is a way out

mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app

ezknives said:
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.

mgoldenberg said:
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.
Click to expand...
Click to collapse
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4

From the fastboot details it looks like the most recent ota
mgoldenberg said:
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Click to expand...
Click to collapse
I say rsd the recent firmware....
Sent from my XT907 using xda app-developers app

sloosecannon said:
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...

mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Try this
I was stuck on the same screen all day
http://www.droidrzr.com/index.php/topic/28162-house-of-moto/

mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4

sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.

mgoldenberg said:
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.
Click to expand...
Click to collapse
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app

zombolt said:
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?

sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/

Did you get your phone back up?... if your on system version .3 or .78 you cannot unlock your boot loader build date 5/2013..
Sent from my XT907 using xda app-developers app

mgoldenberg said:
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/
Click to expand...
Click to collapse
If it didn't work, you're probably already updated. Looks like you can't unlock unfortunately
Sent from my XT907 using Tapatalk 4

mgoldenberg said:
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?
Click to expand...
Click to collapse
Rsd. From that point you should be able to choose whether you want to erase everything or save it. Worked like a charm for me, took about 10min
Sent from my XT907 using xda app-developers app

[Q] Flashed ROM - it rebooted and died?

Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks

re: download/recovery modes
Nurmi_CEO said:
Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks
Click to expand...
Click to collapse
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!

Misterjunky said:
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!
Click to expand...
Click to collapse
Tried....no go still nothing

Nurmi_CEO said:
Tried....no go still nothing
Click to expand...
Click to collapse
Can you link to the specific rom you flashed. It's sounds to me like you might have flashed a bad or wrong rom.

Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.

Nurmi_CEO said:
Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.
Click to expand...
Click to collapse
I can't tell if the t01teatt is for your specific device. I haven't seen the t01te before. I would have expected something different. The symptoms you describe sounds like a bricked device caused by flashing a rom not for your specific device.

I assume your MDL cause you have a custom recovery.
Did you use Auto Loki recovery?
If you didn't use Auto Loki recovery did you flash the Loki doki zip ?
We need all steps you took from start to end before you rebooted your phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app

the phone was bone stock locked att i337. I unlocked it via the service hidden menu on YouTube. it worked fine.
next I rooted it with the motochopper, flashed twrp with goo manager and rebooted to recovery. my first load with twrp seemed to hang up and freeze, so I pulled the battery and rebooted into twrp.
I loaded the liquidsmooth to1att and gapps to be flashed. both seemed to flash successfully, and then I hit restart. forgot to wipe cache and dalvik, planned on rebooting back into recovery to wipe/maybe reflash and wipe cache.
the phone turned off and never turned back on.
I had a T-Mobile sim card in the entire time.
thanks and please help. sending this from my crappy evo lte

Did a little searching and I think the t01te is the note ii. Check out mobiletechvideos.com. they might be able to jtag it.

after root the phone was working fine on the stock ROM.

Nurmi_CEO said:
after root the phone was working fine on the stock ROM.
Click to expand...
Click to collapse
It's the rom you flashed after that which is causing the problem. Like I said I think it was for the note II and not the i337

Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk

rushi.1986 said:
Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
send in for repair? only option? thanks for help

Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
If Odin doesn't recognize it, and I think you said it doesn't, then yea I think that's your only hope. But I'd keep trying to get it into download mode and have Odin recognize it. I haven't seen a hard brick of the i337.
Use the original usb cable, the usb ports in the back of the computer, and if that doesn't work try a different computer.

The build.prop in that ROM you flashed says it is for the SAMSUNG-SGH-I317 which is the Galaxy Note II. That's why it is bricked. Make sure you don't try to flash that one again. If you do get it to come up in download mode make sure you have the correct file before trying to flash again.
Good luck!

Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"

rushi.1986 said:
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"
Click to expand...
Click to collapse
...and end up with an MF3 phone?
It's better to send it off for Jtag like JD said. If it never had the MF3 bootloader on it, there shouldn't be a problem with them putting MDL back on it (as long as there isn't a hardware issue). To me, the cost is well worth it.

scott14719 said:
...and end up with an MF3 phone?
Click to expand...
Click to collapse
Good point! I didn't think of that..

[Q] Can't Boot to Manual Recovery

Hi guys. Since flashing Beans version of KitKat for my Note 3 my phone will no longer boot to manual recovery (volume up, home, power). The phone goes into a boot loop. The phone does reboot normally after the battery is pulled.
Any ideas on what's causing this and how to fix it? Any and all help is appreciated.
Thanks.

sugelover said:
Hi guys. Since flashing Beans version of KitKat for my Note 3 my phone will no longer boot to manual recovery (volume up, home, power). The phone goes into a boot loop. The phone does reboot normally after the battery is pulled.
Any ideas on what's causing this and how to fix it? Any and all help is appreciated.
Thanks.
Click to expand...
Click to collapse
Are you just trying to access safestrap ?

Bobby_z said:
Are you just trying to access safestrap ?
Click to expand...
Click to collapse
No safestrap works fine. I'm referring to the manual recovery mode of the phone. Volume up - Home - Power when the phone is powered off.
If I attempt to reboot to the stock recovery menu (either via the above mentioned method or even after installing the option with Wanam) I get a boot loop.

Never had that issue I did notice when running it I couldn't use the emulator script to enter recovery but was able to power off and manually enter it. Might try to re flash and wipe I don't know if that will fix your issue or not.
Sent from my SM-N900V using XDA Free mobile app

Bobby_z said:
Never had that issue I did notice when running it I couldn't use the emulator script to enter recovery but was able to power off and manually enter it. Might try to re flash and wipe I don't know if that will fix your issue or not.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
I've tried reflashing and wiping already. No luck.

Not sure then best advise I could give you is stay on 4.3 for a while I didn't really think 4.4 was that great plus not a lot of rom option's just yet.
Sent from my SM-N900V using XDA Free mobile app