HELP! - T-Mobile Samsung Galaxy Note II

Came from the lg g2x, which made me unfortunately quite familiar with having to mod the device. Used to use cwm. Tried twrp for the first time with this device. Love this device, had jedi 6 running fine, then decided to flash jedi x6. Did all the usual stuff, except i have not been able to escape a bootloop/no service with this rom, and trying to go back and restore backups results in the same bootloop. Please help!

Check your modem and kernel
Sent from my SGH-T889 using xda app-developers app

Make 100% sure you're using the right files for your specific device. I've accidentally downloaded the wrong versions of things before & had the same problems you describe. Try installing Jedi 6 again & see if that will load. Also, try re-downloading x6, you could just have had a corrupted download.
I've had issues with TWRP in the past too. I hard-bricked my GSII using TWRP to do a factory reset back in August & since then, I've been too spooked to use it again. Try going back to CWM & see if you can flash successfully with that.

getting frustrated for sure. Zapped twrp. Now just have access to download mode. Downloaded and attempted to flash stock recovery, but it won't get past the md5 stage, saying the hash value is invalid. HELP!!!

Try re-downloading.
Hastily spouted for your befuddlement

Coug76 said:
Try re-downloading.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Oh I have the befuddlement angle covered quite well. Wondering if it's because this is only the tar and md5, no boot image or modem?

Do I need to unroot via odin somehow first?

Or could it be a debugging issue since I can't boot to enable this?

SUCCESS! Finally tried flashing the rooted stock tar found in the dev section. Thank you !!

You probably forgot to wipe the cache.

Related

[Solved] $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)

Basically this is what happened, I rooted my phone using TeamEpic-Root-from-Recovery-v5.zip and CWM-Recovery-LTE-SGS3-v5.tar.zip with Odin without any problems. Then I tried tampering with the framework-res.apk and I thought I did it correctly, I replaced it with the current res in the /system/framework folder of the internal sd. Then I rebooted my phone and bam stuck at the Samsung Galaxy S III screen. I've now tried finding a way to get into the internal sd card to replace the framework-res.apk back to original but my computer wont recognize it when in recovery or downloading mode. I have trying reflashing Clockworkmod several times and I've tried wiping the cache and factory reset. When I factory reset it says error mounting sd card, aborting. I am now out of ideas as to how to fix it and I'm not sure what to do with PIT files, which could be a possible solution. I am running Tmobile's Galaxy S3 T-999 16gb. All that being said, anyone who can help me get my phone back up and running I will reward you with $10 through paypal, because that's how desperate I am to fix my phone before someone finds out I bricked it!
Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app
camacho.kyle said:
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, what do you mean by reinstall drivers, like kies? I can't flash any rom's because I can't transfer the zip files over to the sd card since my phone won't recognize it since it won't go past the samsung screen. All I can do is flash clockwork mod from odin like .md5 and .tar. If I install a lower version of Odin what version did you use, and do you think flashing clockwork mod will be able to replace the framework-res.apk through odin?
Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
iAmYoungSpiffy said:
Thanks for the reply, what do you mean by reinstall drivers, like kies?
Click to expand...
Click to collapse
Reinstall the drivers for Odin, and you can even try reinstalling Kies too. Make sure you restart your pc after you reinstall kies and the drivers.
Sent from my SGH-T999 using xda app-developers app
Are the files you flashed for a I9300? They do not look familiar to me.
Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Aerowinder said:
Are you using a SGH-T999 or an I9300? If the former, use the links in my signature. Should fix it if it's not hosed.
Uninstall Kies (and the drivers if the Kies uninstall doesn't do it).
You may want to Odin a stock rom. If you do, it it before flashing a recovery.
Click to expand...
Click to collapse
He's using a T999
Sent from my SGH-T999 using xda app-developers app
camacho.kyle said:
He's using a T999
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Do you think changing the clockworkmod .tar.md5 file and flashing something different will have any affect? If so, what do you suggest?
Check out my signature, it has everything you should need (save the OS you want).
Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Wow thanks for that clockworck mod! It has much more features than v5 I'm gonna play around with it and see what I can come up with.
Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Thank you for the files, I'm now able to flash roms from my sd. I"ve flashed your clockwork and superuser. However, when I load up the phone I'm still getting stuck at the samsung logo
no external sdcard?
Did you try to flash another rom? What were you using, and what did you flash?
Why are you trying to fix a bricked ROM with CWM?
Just Odin a stock rom, and work from there. I don't know why you would keep trying to reflash recovery, that isn't going to do squat for you.
Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott
mt3g said:
no external sdcard?
Click to expand...
Click to collapse
I do, 64gb
Aerowinder said:
Did you try to flash another rom? What were you using, and what did you flash?
Click to expand...
Click to collapse
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?
You can't flash a rom from your external sdcard? or your internal? or either?
sbaeder said:
Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott
Click to expand...
Click to collapse
I've now tried flashing Team Epic's ROM and I've wiped all cache restored to factory settings wiped dalvik cache, no progress.
mt3g said:
You can't flash a rom from your external sdcard? or your internal? or either?
Click to expand...
Click to collapse
Now that I updated my clockwork mod I'm able to flash from my sd card. Trouble for me is finding the right ROM that is compatible and appealing. I've tried a few now and whenever I flash them I go to boot up the phone and I get stopped on the samsung galaxy s iii logo. There has to be a way to wipe everything and flash a fresh clean rom. I've stayed up till 2 in the morning only to get up at 6 in the morning two nights in a row now totaling almost 10 hours of trying to fix my phone
iAmYoungSpiffy said:
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?
Click to expand...
Click to collapse
From this quote it seems that you are flashing TWRP recovery and the flashing CWR right after it. That makes no sense. I don't use CWR on this phone but have used it before. So I'm not sure that LTE should be in the description as T999 isn't an LTE device. I could be wrong though. You can get an Odin-able version of either TWRP or CWR from this page.
Go here and download the stock image TMO T999UVDLJA. Follow the directions in the OP (make sure you unzip it first. Read and then read it again) . Fire up Odin and put the Root66 tar in the PDA slot (nothing in PIT). Flash the Root66. It will take about 5 minutes or so. Once it says Pass it should reboot. It WILL bootloop. If you have already flashed EITHER TWRP or CWR, then boot into recovery and Factory Reset. If you haven't flashed EITHER TWRP or CWR, then pull your battery and boot back into Download Mode. From there you put EITHER TWRP or CWR into the PDA slot and flash it. Pass. The reboot into recovery and Factory Reset.
First boot will take the longest bc it has to rebuild the /cache and /dalvik-cache. Let's get you up and running before you move on to flashing a custom ROM, OK?

Boot loop at Samsung welcome screen when attempting clean install.

I am currently running SkyNote Air and want to do a clean wipe and start fresh. I've done this before without a problem but am having trouble this time around. After a clean wipe and ROM install, the phone will boot but after seeing the "Android is upgrading, Starting Apps" screen and momentarily displaying the Welcome screen the phone will go into a loop. Seems to happen after the phone connects to the network. I can interact with it to reboot into recovery if I'm quick enough.
From the searches I've done, I've already tried clearing cache and Dalvik and factory reset without any luck. I used Philz to wipe for a new ROM and TWRP to wipe internal storage as well without any luck. I've tried installing the ROM twice before rebooting recovery. Fix Permissions from TWRP also hasn't helped. I already had the 43paramtz.tar flashed and reflashing it does not help either. I have not tried the One-click method yet. That seems the only thing left to try. Just want to see if anyone else has any suggestions. Thanks in advance!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
ojai00 said:
I am currently running SkyNote Air and want to do a clean wipe and start fresh. I've done this before without a problem but am having trouble this time around. After a clean wipe and ROM install, the phone will boot but after seeing the "Android is upgrading, Starting Apps" screen and momentarily displaying the Welcome screen the phone will go into a loop. Seems to happen after the phone connects to the network. I can interact with it to reboot into recovery if I'm quick enough.
From the searches I've done, I've already tried clearing cache and Dalvik and factory reset without any luck. I used Philz to wipe for a new ROM and TWRP to wipe internal storage as well without any luck. I've tried installing the ROM twice before rebooting recovery. Fix Permissions from TWRP also hasn't helped. I already had the 43paramtz.tar flashed and reflashing it does not help either. I have not tried the One-click method yet. That seems the only thing left to try. Just want to see if anyone else has any suggestions. Thanks in advance!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Are you on T-mobile ?
dicksteele said:
What bootloader are you on ??? Did you do the 4.3 OTA ?
Click to expand...
Click to collapse
I believe I am on a 4.1.2 bootloader (I317UCAMA4). I have not restored to stock or done a 4.3 OTA.
ojai00 said:
I believe I am on a 4.1.2 bootloader (I317UCAMA4). I have not restored to stock or done a 4.3 OTA.
Click to expand...
Click to collapse
And you're on T-Mobile ?
dicksteele said:
And you're on T-Mobile ?
Click to expand...
Click to collapse
Yep. Using an unlocked i317 on T-Mobile with the AWS Mod. My first instinct was to remove the SIM since the phone seemed to be restarting once I was connected to the network but that didn't work either.
ojai00 said:
Yep. Using an unlocked i317 on T-Mobile with the AWS Mod. My first instinct was to remove the SIM since the phone seemed to be restarting once I was connected to the network but that didn't work either.
Click to expand...
Click to collapse
Ahhhh.. Like it says in your signature.... :cyclops:
Yea I'm awake.
Have your ever flashed anything else besides Sky Air ? That's the one you have reflashed after Philz/TWRP wipes right ?
dicksteele said:
Ahhhh.. Like it says in your signature.... :cyclops:
Yea I'm awake.
Have your ever flashed anything else besides Sky Air ? That's the one you have reflashed after Philz/TWRP wipes right ?
Click to expand...
Click to collapse
SkyNote is the only 4.3 ROM I've tried. Yes, that was the ROM I reflashed after the full wipes. I've been flashing SkyNote from version 8 onwards and am now running the N3 version. I've seen some people have issues with the N3 version but not the Vanilla version. I haven't tried that one. I've been following MeanBean but I'm worried if I can't even get a reinstall of SkyNote Air working my chances of another ROM will probably be the same!
ojai00 said:
SkyNote is the only 4.3 ROM I've tried. Yes, that was the ROM I reflashed after the full wipes. I've been flashing SkyNote from version 8 onwards and am now running the N3 version. I've seen some people have issues with the N3 version but not the Vanilla version. I haven't tried that one. I've been following MeanBean but I'm worried if I can't even get a reinstall of SkyNote Air working my chances of another ROM will probably be the same!
Click to expand...
Click to collapse
MeanBean is pretty sweet. You have to remember to run the fixdata.sh.
I'm thinking you should give this a try, a stock ROM.
http://forum.xda-developers.com/showthread.php?t=2589891
It's still flashing from a custom recovery.
You've done everything short of sacrificing a chicken.
Gotta run to a mind numbing meeting.....
dicksteele said:
MeanBean is pretty sweet. You have to remember to run the fixdata.sh.
I'm thinking you should give this a try, a stock ROM.
http://forum.xda-developers.com/showthread.php?t=2589891
It's still flashing from a custom recovery.
You've done everything short of sacrificing a chicken.
Gotta run to a mind numbing meeting.....
Click to expand...
Click to collapse
I'll give it a shot. Good luck with the meeting. Thanks for your help! :highfive:
ojai00 said:
I'll give it a shot. Good luck with the meeting. Thanks for your help! :highfive:
Click to expand...
Click to collapse
Good luck.... Hopefully it works.
Tried flashing the stock deodexed ROM in Philz and still the same result. I can at least make it far enough to the home screen but am still getting the same reboots. I also upgraded to the 4.3 bootloader from seanz thread here (http://forum.xda-developers.com/showthread.php?t=2502464) without luck. I wonder if flashing the ROM in Odin will be any different? I have my doubts but want to hear it from someone else.
ojai00 said:
Tried flashing the stock deodexed ROM in Philz and still the same result. I can at least make it far enough to the home screen but am still getting the same reboots. I also upgraded to the 4.3 bootloader from seanz thread here (http://forum.xda-developers.com/showthread.php?t=2502464) without luck. I wonder if flashing the ROM in Odin will be any different? I have my doubts but want to hear it from someone else.
Click to expand...
Click to collapse
If you're game you could try this
http://forum.xda-developers.com/showthread.php?t=2618447
If you do sections 1 and 2, and don't get boot loops, you can flash that stock/root/odex ROM.
dicksteele said:
If you're game you could try this
http://forum.xda-developers.com/showthread.php?t=2618447
If you do sections 1 and 2, and don't get boot loops, you can flash that stock/root/odex ROM.
Click to expand...
Click to collapse
Thanks again. I'll try that next. Attempting the Odexed version of Zen's package first.
ojai00 said:
Thanks again. I'll try that next. Attempting the Odexed version of Zen's package first.
Click to expand...
Click to collapse
Sounds good. Good luck.
Not sure what is residual and causing the boot loops.
So I dirty flashed the odex version and that seems to be stable. I then factory reset to wipe it clean and that came up fine. Going to try wiping completely and installing Stock Odex again.
Update: Rooted Stock Odex seems to be the only one that is booting up fine. I then flashed SkyNote Air without any wipes and it was fine again. Once I tried to factory reset to defaults after Air is installed (wiping cache and Dalvik in the process), the boot loops begin. Guess this is what I'm going to have to do if I want to start fresh on any ROM.
ojai00 said:
So I dirty flashed the odex version and that seems to be stable. I then factory reset to wipe it clean and that came up fine. Going to try wiping completely and installing Stock Odex again.
Update: Rooted Stock Odex seems to be the only one that is booting up fine. I then flashed SkyNote Air without any wipes and it was fine again. Once I tried to factory reset to defaults after Air is installed (wiping cache and Dalvik in the process), the boot loops begin. Guess this is what I'm going to have to do if I want to start fresh on any ROM.
Click to expand...
Click to collapse
Too wierd. At least you found a path.... Not optimal, but functional.
I'm fighting why I can't flash a custom recovery now.
dicksteele said:
Too wierd. At least you found a path.... Not optimal, but functional.
I'm fighting why I can't flash a custom recovery now.
Click to expand...
Click to collapse
Just a thought even though I'm sure you verified. You're sure you're trying to flash the proper recovery for the device? I know TWRP and Philz make a specific version for the i317 with t0lteatt in the file name.
ojai00 said:
Just a thought even though I'm sure you verified. You're sure you're trying to flash the proper recovery for the device? I know TWRP and Philz make a specific version for the i317 with t0lteatt in the file name.
Click to expand...
Click to collapse
Yepper. They live on my machine and phone. Thought it was an ODIN thing, just rooted my phone.
I do so much crap to it maybe that's was I was missing .... We'll see.
EDIT : And that was it. Interesting .....

Cannot get past boot logo on any ROM

Of all the things I have screwed up, I can't believe my first post asking for help is this one. I have been rooting and installing custom ROM's since the EVO. Always found the help I needed in someone else' thread. But this has me stumped.
I am a ROM jumper. Do it all the time. Yesterday, I was having some performance issues with my Note2 so I thought I would do a full wipe and try out another ROM. I also wiped my internal storage. My recover at that time was philz_touch_6.19.3-t0ltetmo. Somehow, I ended up wiping everything and I couldn't boot into anything other than Download mode.
Still no biggie. Wait until I got home and I would flash some with via Odin on my Windows netbook. It never worked. It would maybe get to 25% complete and hang. I left it running for about an hours with no results. Then I moved to my Linux desktop and installed Heimdall. Used that to put philz_touch_6.19.3-t0ltetmo back on the device. Then I installed cm-10.2-20140309-NIGHTLY-t0ltetmo.zip via sideload.
Stuck on smiling robot with a circle.
So I sideloaded CARBON-KK-NIGHTLY-20140302-0859-t0ltetmo.zip. Stuck on the logo there too. aokp_t0ltetmo_kitkat_nightly_2014-02-25.zip same thing. I try pushing the ROM's instead of sideloading. No luck.
So I am thinking that maybe I got a bad philz recovery. Redownload that, and go through the same list of roms. Nothing. OK... so maybe philz has become a POS for some reason on my phone. I try openrecovery-twrp-2.7.0.0-t0ltetmo.zip and repeat all the steps above. Wiping and sideloading, then wiping and pushing... stuck on logo.
I have to say I am stumped. I am losing nerd cred by asking for help, but dammit I am stumped. Any help appreciated.
Most phones have been recovered by flashing stock image, you can give it a shot.
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
Most phones have been recovered by flashing stock image, you can give it a shot.
Click to expand...
Click to collapse
Eww. Does that have to be flashed via Odin/Heimdall or can I use my established recovery? Also, I looked at some of those earlier and they are all in ZIP format. Odin wants TAR.MD5. Is it as simple as unziping and then tar-ing? I don't see an option to TAR.MD5.
marriedman said:
Eww. Does that have to be flashed via Odin/Heimdall or can I use my established recovery? Also, I looked at some of those earlier and they are all in ZIP format. Odin wants TAR.MD5. Is it as simple as unziping and then tar-ing? I don't see an option to TAR.MD5.
Click to expand...
Click to collapse
The easiest option would be to flash the tar.md5 file using ODIN.
If you are 4.3 bootloader you can flash this MrRobinson's ROM
http://www.androidfilehost.com/?fid=23252070760975435
If you are 4.1.2 bootloader you can flash this ROM, download link on post#1
http://forum.xda-developers.com/showthread.php?t=2636552
If you plan to flash it using Heimdall you will have to first extract the tar.md5 file and then flash all ROM components.
Your command should be something like this, please note I have not tried flashing using Heimdall so I am not 100% it will work.
sudo heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin
ciphercodes said:
The easiest option would be to flash the tar.md5 file using ODIN.
If you are 4.3 bootloader you can flash this MrRobinson's ROM
http://www.androidfilehost.com/?fid=23252070760975435
If you are 4.1.2 bootloader you can flash this ROM, download link on post#1
http://forum.xda-developers.com/showthread.php?t=2636552
Click to expand...
Click to collapse
Good stuff, thank you cipher.
Perhaps I am missing something here though. I went to check which version bootloader I have. I just assumed I would have 4.3 since I have been running JB & KK rom's for the past month or so; but I wanted to double check. When I boot into recovery, it doesn't show it there. When I boot into download mode, it doesn't show it there either. Where should I be seeing the version number?
When you boot into download mode do you see KNOX Warranty Void below system status ?
If not then your phone is not on 4.3 bootloader.
Sent from my SGH-T889 using xda app-developers app
Yes, it shows KNOX WARRANTY VOID: 1
So then I have 4.3. Thanks for the info. When I get home tonight, I will try and flash MrRobinson's ROM then report back. Thank you for the help & I will post my results then.
Well, that took care of it. I was able to use MrRobinson's ROM & Heimdall. I did have to download a PIT file, but that was easily found here on xda. Within minutes I had the gawd awful Samsung TW blooping and making stupid noises. Went ahead and flashed TWRP and I am downloading CarbonRom now.
Thanks for the help cipher. It was driving me nuts.
um... mark as solved?
I tried to edit my original post to mark it as solved, but there isn't an option. How do I change my title?
Well, I spoke too soon. I just discovered that I have no cell service. Went to look and found I have no IMEI # anymore. WTF?
Looks like you flashed a modem for a different device.
No worries, just flash the modem from Mr Robinsons ROM and that should take care of it.
Sent from my SGH-T889 using xda app-developers app
I wish it were that simple. I just reflashed MrRobinsons and it is back to Samsung recovery and rom. Still no IMEI. I am going to go full retard and flash the one from SamMobile. I'll erport back later.
Mrrobinsons ROM is the stock rom, it's just root injected and Knox-free.
Try KIES emergency recovery method.
You can find link for procedure in this forum in one of the posts.
Sent from my SGH-T889 using xda app-developers app
Just saw this and I am on my way to work. With no Admin priviledge there, I will have to try this when I get home.
I appreciate the time you have taken to help me cipher.
OKay, I downloaded Kies and it saw my phone. However, it says my phone is fine and will not do an emeregency recovery. After searching on here some more, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2261153
It's possible that Emergency Recovery is no more. I am just about done with this phone. It's been three days and I need a working phone again.
marriedman said:
Of all the things I have screwed up, I can't believe my first post asking for help is this one. I have been rooting and installing custom ROM's since the EVO. Always found the help I needed in someone else' thread. But this has me stumped.
I am a ROM jumper. Do it all the time. Yesterday, I was having some performance issues with my Note2 so I thought I would do a full wipe and try out another ROM. I also wiped my internal storage. My recover at that time was philz_touch_6.19.3-t0ltetmo. Somehow, I ended up wiping everything and I couldn't boot into anything other than Download mode.
Still no biggie. Wait until I got home and I would flash some with via Odin on my Windows netbook. It never worked. It would maybe get to 25% complete and hang. I left it running for about an hours with no results. Then I moved to my Linux desktop and installed Heimdall. Used that to put philz_touch_6.19.3-t0ltetmo back on the device. Then I installed cm-10.2-20140309-NIGHTLY-t0ltetmo.zip via sideload.
Stuck on smiling robot with a circle.
So I sideloaded CARBON-KK-NIGHTLY-20140302-0859-t0ltetmo.zip. Stuck on the logo there too. aokp_t0ltetmo_kitkat_nightly_2014-02-25.zip same thing. I try pushing the ROM's instead of sideloading. No luck.
So I am thinking that maybe I got a bad philz recovery. Redownload that, and go through the same list of roms. Nothing. OK... so maybe philz has become a POS for some reason on my phone. I try openrecovery-twrp-2.7.0.0-t0ltetmo.zip and repeat all the steps above. Wiping and sideloading, then wiping and pushing... stuck on logo.
I have to say I am stumped. I am losing nerd cred by asking for help, but dammit I am stumped. Any help appreciated.
Click to expand...
Click to collapse
Ok first off, dont have tmobile, but i do have a note (verizon)
What do you mean when you say you are "sideloading" "pushing" a ROM.. Bc normally in recovery you "flash" a rom.
So let's make sure you are doing just that..?
If you are "flashing" a rom in recovery and it installs and you reboot and you are stuck.. thats a different issue..
I would recommend getting your stock Odin tar and flashing it..Make sure it contains a boot.img and if you guys use a pit file.. use that as well..
Post here with some answers and results..Lets see if we can get you back in buisness..
I have HARD bricked my phone, fired eMMC, softed bricked..pretty much been through everything so hopefully we can figure it out!:good:
The main thing is DON'T get frustrated.. I know it's hard but that when you make mistakes and PANIC
lacoursiere18 said:
What do you mean when you say you are "sideloading" "pushing" a ROM.. Bc normally in recovery you "flash" a rom.
So let's make sure you are doing just that..?
Click to expand...
Click to collapse
Originally, I could not boot into any rom. I could get into recovery. In order to get a rom onto the phone, I could download the zip file to my computer and inside the recovery turn on sideload to move the file to the phone and flash. And Even then I never got any of the roms to get past the boot logo. Cyanogenmod, Carbon-rom, AOKP... none of them.
I would recommend getting your stock Odin tar and flashing it..Make sure it contains a boot.img and if you guys use a pit file.. use that as well..
Click to expand...
Click to collapse
Yup, I did that. I tried doing it through Heimdall since I am a Linux guy. I can install a stock or stock based rom, but there is never a IMEI number. From what I can tell, the EFS partition is just gone & I never backed it up. I lost the IMEI and it is not coming back.
The main thing is DON'T get frustrated.. I know it's hard but that when you make mistakes and PANIC
Click to expand...
Click to collapse
Oh, I agree. I stepped away from it for about 8 hours a day while at work. Thats when I did most of my reading though. I am pretty sure this is going up for sale on ebay this week. I already bought a new phone. Thank you for taking the time to reply though.
marriedman said:
Originally, I could not boot into any rom. I could get into recovery. In order to get a rom onto the phone, I could download the zip file to my computer and inside the recovery turn on sideload to move the file to the phone and flash. And Even then I never got any of the roms to get past the boot logo. Cyanogenmod, Carbon-rom, AOKP... none of them.
Yup, I did that. I tried doing it through Heimdall since I am a Linux guy. I can install a stock or stock based rom, but there is never a IMEI number. From what I can tell, the EFS partition is just gone & I never backed it up. I lost the IMEI and it is not coming back.
Oh, I agree. I stepped away from it for about 8 hours a day while at work. Thats when I did most of my reading though. I am pretty sure this is going up for sale on ebay this week. I already bought a new phone. Thank you for taking the time to reply though.
Click to expand...
Click to collapse
Have you tried flashing the latest firmware, and if yes is this where you got it?
http://forum.xda-developers.com/showthread.php?t=2102380
Also did you read post #2 about going back into recovery, do a factory reset and reboot?
And were you getting these roms that would loop you in this forum, just making sure i know it may sound stupid..
Also, what was the estimated time you were waiting for them to boot..5mins, 10mins, 20mins.. Some take longer than others..
The only other thing i could suggest is JTAG services, by MobileTechVideos, the owner's name is Josh, stand up guy, and I belive it much cheaper than buying a new device =)
lacoursiere18 said:
Have you tried flashing the latest firmware, and if yes is this where you got it?
http://forum.xda-developers.com/showthread.php?t=2102380
Also did you read post #2 about going back into recovery, do a factory reset and reboot?"
Click to expand...
Click to collapse
Yep & yep. I also tried MrRobinsons root injected rom before going this route.
And were you getting these roms that would loop you in this forum, just making sure i know it may sound stupid..
Also, what was the estimated time you were waiting for them to boot..5mins, 10mins, 20mins.. Some take longer than others..
Click to expand...
Click to collapse
I have had some take as long as 20 minutes before, but that was rare. This time, I actually fell asleep and when I woke up in the morning, it was still on the animated boot logo and hot as hell. Still going though. So it was at least 6 hours thst timr.
The only other thing i could suggest is JTAG services, by MobileTechVideos, the owner's name is Josh, stand up guy, and I belive it much cheaper than buying a new device =)
Click to expand...
Click to collapse
I've not heard of this, I'll look them up. Thanks!

OMG HELP! Bootloop, download modes works, flashed with Kies and STILL bootlooping

I have the SGH-M919
I've rooted my phone and was running a GE rom
Everything was fine for MONTHS
Got in my car and plugged my AUX cable to my phone for music and the phone froze.
Force rebooted the phone and it started boot looping.
Rebooted to recovery (TWRP) and TRIED to wipe dalvik and cache and it FAILED, said it couldn't mount dalvik
Rebooted to recovery again and wiped all partitions and this time it worked so I proceeded to re-install GE rom, still bootlooping
Came home and tried to use ODIN to flash M919UVUAMDL and it failed.
Tried ODIN to flash M919UVUEMK2, also failed (sorry don't have the error messages right now)
Rebooted phone into download mode again and phone said there was an issue and to use Kies to recover
Installed Kies and started emergency recovery and that went through fine and the phone finished and STILLLLLLL BOOT LOOPS !!!!!!!!!!!
Copied the file that Kies downloaded (M919UVUFNB4) and tried ODIN again to flash that and it flashes fine but STILLL BOOT LOOPS
Obviously my Knox warranty flag is tripped and I don't have the money for the insurance right now.... so PLEASE FOR THE LOVE OF BOB does anyone have any other diagnostic tips or tricks to help me figure out why the F this phone is boot looping.
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
avelis26 said:
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
Click to expand...
Click to collapse
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
lalec said:
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
1. Samsung WON'T reset my flag... they won't even TOUCH the phone in any way shape or form. I spent almost two hours dealing with them and being honest about the situation. And they STILL won't do anything at all. The rep I was speaking too even said the first thing they do is check that flag and if its popped, they put it back in the box and send it back with no further action. So I will not buy form Samsung ever again.
2. I'm not expecting instant responses at all and nothing I said should have been interpreted at such. I made the comment of 53 views in 4 hours and not a single reply ... I was hoping for a better ratio of responses than that.
3. Where are you getting "Not doing a full wipe before installed a different ROM..." I never said that I didn't... and if you read what I took the time to organize neatly, I specifically state that full wipe was what I tried BEFORE re-installing the SAME rom.
4. Can't try a different recovery if I can't even get the stock factory image to do an initial boot.
cybervyrus8587 said:
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
Click to expand...
Click to collapse
Which one did you flash ?
M919UVUFNB4
M919UVUEMK2
M919UVUAMDL
M919UVUAMDB
I've tried #3 but it gives me an auth failure....
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
avelis26 said:
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
Click to expand...
Click to collapse
Post deleted
☞ Sent from here ☜
baseballfanz said:
Post deleted
☞ Sent from here ☜
Click to expand...
Click to collapse
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Ok so .... I guess installing PhilZ... then full wipe, then flashing M919UVUFNB4 TWICE back to back did the trick.... no freaking clue how but it worked
I spoke too soon. Went through first boot. Got all the way to the end setup and then it rebooted on its own ... and now its stuck in a boot loop again
avelis26 said:
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Click to expand...
Click to collapse
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
TigerDNA said:
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
Click to expand...
Click to collapse
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
avelis26 said:
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
Click to expand...
Click to collapse
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
TigerDNA said:
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
Click to expand...
Click to collapse
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Yea your Knox flag is tripped alright, you have zero chance if ever getting back to 0x0.... Nobody knows how to do that brother.
Sent from my GT-I9505G using xda app-developers app
avelis26 said:
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Click to expand...
Click to collapse
Just put the phone in download mode. Power off then volume up, home and power. You'll see it when you get into download mode.
TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
Philz's and TWRP both had small glitches on the GS4 4.2.2 Stock Rom.
I downloaded and installed the OUDHS-Recovery-jfltetmo-1.0.3.3.tar and have it all PERFECT now! You can search using exactly that filename and download it for your use. IT IS THE flashable Recovery Version.
I can, using Rom Manager, NAME THE BACKUP before booting into recovery, and it makes the backup just as I named it!
I can also recover using Rom Manager, and visually select what backup file I want to restore to, again, before booting into recovery!
CWM type backups take longer then TWRP backups to complete, but I have not had any instance that a backup I made couldn't be restored.
I did have that problem using "TWRP" and "On Line Backup". (No longer do I trust using those)
Hope this info helps your decision!
Good Luck and Aloha!

[RESOLVED] Help! My phone is stuck on the AT&T Logo!

I am returning my phone to my dad because i'm getting an upgrade and he wants to sell it, so i tried to revert to stock from CM12.1 unofficial nightlies. I flashed the FNJ1 system and boot.img. my phone was on FNJ1. now it's stuck on the at&t logo and i cant do anyhting, any help?
AT&T SGH-I747 UCUFNJ1 CM12.1 unofficial nightly.
Edit: In the mean time i've reverted to cm12 but i still need to revert to stock so any help is greatly appreciated.
You have to factory reset after flashing back to stock. If you are going to sell it, I suggest doing so from stock recovery.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You have to factory reset after flashing back to stock. If you are going to sell it, I suggest doing so from stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I reflashed the FNJ1 rom and then factory reset afterwards and it still hangs at the AT&T boot logo, any other suggestions?
Where did the rom come from exactly? There are a few that I've seen. Did you check the md5 to make sure the download wasn't corrupted?
Can you verify your bootloader / baseband?
Using terminal emulator (twrp has one built in) enter this.
getprop ro.bootloader
getprop ro.baseband
Let us know what it says.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Where did the rom come from exactly? There are a few that I've seen. Did you check the md5 to make sure the download wasn't corrupted?
Can you verify your bootloader / baseband?
Using terminal emulator (twrp has one built in) enter this.
getprop ro.bootloader
getprop ro.baseband
Let us know what it says.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i used Enewman's fnj1 system and boot.img from the general forum here. and i cant boot into recovery only download mode, but i know for sure it was ucufnj1
also the other post is me:
We will need more detailed info if you don't mind.
What were you on before? cm 12.1
What "stock rom" and what recovery exactly did you flash. enewman's fnj1
How did you flash? cwm
You said it "still doesn't boot" but we're able to flash it, do you mean it just won't boot android? yes
Can you boot download mode? yes
What was wrong that made you need to flash the rom and recovery to make it boot, and how did it get to that point to begin with? need to get to stock to sell, wouldnt boot, and the soft brick help said to try flashing stock recovery.
I managed to boot into recovery by flashing an older version of CWM via Odin. i flashed CM12.1 back again and it boots! thank god i have a phone again. any ideas as to what is causing the softbrick?
Hard to say. I do know that enewman17 recommends flashing with twrp, and that's what most people have used AFAIK. So there may be something about the newer cwm that executes the script a little differently. That's purely a guess though. Could've just been a bad flash for whatever reason.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Hard to say. I do know that enewman17 recommends flashing with twrp, and that's what most people have used AFAIK. So there may be something about the newer cwm that executes the script a little differently. That's purely a guess though. Could've just been a bad flash for whatever reason.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Should I try flashing twrp and then flashing the stock rom?
if i'm not mistaken CWM has pretty much been abondoned and no longer updated.
twrp and philz are preferred.
then again , "couldve just been a bad flash for whatever reason".
"all i can really do is stay out of my own way and let the will of heaven be done"
l3gionaires said:
Should I try flashing twrp and then flashing the stock rom?
Click to expand...
Click to collapse
You can try it if you like. Keep cm available just in case though. You might try some of the other stock builds too. Check the general and development section. I think there's about 3 NJ2 roms, each done a little differently.
Sent from my SGH-T999 using Tapatalk
mrrocketdog said:
if i'm not mistaken CWM has pretty much been abondoned and no longer updated.
twrp and philz are preferred.
then again , "couldve just been a bad flash for whatever reason".
"all i can really do is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
TWRP is a million times better! works great thanks for the suggestion!
DocHoliday77 said:
You can try it if you like. Keep cm available just in case though. You might try some of the other stock builds too. Check the general and development section. I think there's about 3 NJ2 roms, each done a little differently.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i updated my bootloader and modem to nj2 then flashed the stock rom for nj2 (this time using TWRP) and had the same outcome, it just hangs on the AT&T logo. I think this phone is doomed to be a CM12.1 phone.
That's strange. Did you try a different one if the NJ2 stock roms as well?
Oh and did you check the md5 to make sure the download wasn't corrupted?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
That's strange. Did you try a different one if the NJ2 stock roms as well?
Oh and did you check the md5 to make sure the download wasn't corrupted?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
all md5s match and i tried enewman's deodexed fnj2 roms as well and it still hangs at AT&T Logo. maybe it's an issue of returning from Lollipop to KK?
Check the cm rom threads. Maybe someone else there has run into a similar problem. I don't use it myself, so I'm not familiar enough with it to say.
I'll try to do a little digging when I get home. There's got to be some sort of explanation!
(Have you ever tried reformatting /system to anything other than ext4? )
Sent from my SGH-T999 using Tapatalk
---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------
Maybe try another TW custom rom. Just to see if it does the same thing.
Sent from my SGH-T999 using Tapatalk
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
dawgdoc said:
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
Click to expand...
Click to collapse
i'll try these when I get home and update asap
also @ DocHoliday I don't Know how to do that
dawgdoc said:
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
Click to expand...
Click to collapse
l3gionaires said:
i'll try these when I get home and update asap
also @ DocHoliday I don't Know how to do that
Click to expand...
Click to collapse
#1 worked for me! for some reason when i was on NJ1, the recovery didn't work, so i guess updating to NJ2 fixed it? anyways who cares! I'm back to fully bloated TW! Thank you guys for all your help!
l3gionaires said:
#1 worked for me! for some reason when i was on NJ1, the recovery didn't work, so i guess updating to NJ2 fixed it? anyways who cares! I'm back to fully bloated TW! Thank you guys for all your help!
Click to expand...
Click to collapse
Glad to hear it worked. :victory: Now to find a buyer.

Categories

Resources