I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Yorgo1982 said:
have the same issue a man on xda helped me to get a nandroodmfrom is phone now my phone boot but no network cause i force flash the south america modem, and i have error msg. process system in not reponding and it boot. do u have an errormmsg too?
Click to expand...
Click to collapse
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Apra24 said:
I got an error message trying to flash a SAM firmware. It would just say FAILED in red letters. I'm going to try the Mexico one next, and hopefully it will work. I'm hoping someone could upload a working backup from their phone.
Click to expand...
Click to collapse
wait sammobile if u r with rogers bell telus fido vmc koodo, and if with other carrier contact them with ur phone model and serial num so they will upload it ..
Apra24 said:
I'm with Bell (Canada.) I was hesitant to root this device as it's a pretty significant investment, but I have rooted my original note with few issues, so I figured it should work as long as I follow every step carefully. Well unfortunately, upon first trying to root it, apps would start updating right at bootup, and SuperSU continuously crashed. So I decided I was just going to restore it to my original state and be done with it for now. Nope. Once I did this, the phone would just enter a boot cycle. (How does restoring my backup place me into a boot cycle?)
The only SM-N900W8 firmware downloads I can find are for south american regions... I have tried one of them and it failed to install. I am a bit panicked at the moment. Is there some crucial step I'm missing here?
Click to expand...
Click to collapse
Did you restore from CWM/TWRP?
Pikezer1337 said:
Did you restore from CWM/TWRP?
Click to expand...
Click to collapse
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Apra24 said:
TRWP. I'm in the process of uploading a zip of my backup through hotfile, if anyone else who is having the same problem would want to try it out..
Click to expand...
Click to collapse
If you restored through TWRP there is a good chance that you are softbricked. There are restoring issues that mess with the system partition.
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Apra24 said:
Update: I was able to flash the tar file from inside the zip of mexican firmware through odin (I was trying to install the zip through TWRM before... perhaps you need to install stock firmwares through odin? It's been a while.)
It's not rooted, and the icons are all different looking... but it's back in working condition
Click to expand...
Click to collapse
can u give the file name?
plz
Yorgo1982 said:
can u give the file name?
plz
Click to expand...
Click to collapse
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Apra24 said:
I am using the TCE (Mexican) firmware from this link (It won't let me post links since I'm a newly registered account on these forums, but if you google "n900w8 firmware site:samsungis.com" it will be the first result)
I unzipped the file and flashed the tar file within using odin.
Click to expand...
Click to collapse
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Yorgo1982 said:
Not working having same prob and same msg pop up. Means my phone is a factory damaged. And since i rooted it we will see what they will do at sammy lol
Click to expand...
Click to collapse
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
Could this be a Knox created problem? The reason I say this is you were able to restore a "new" (unknown to Knox) firmware, but it failed on the second time (as it is now no longer newer). I wonder if you were able to find a firmware with a later number (ex ...H2 rather than ...H1) it would install?
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I'm wondering if the official Bell/Rogers firmware will be available any time soon? Does it typically get released soon after the phone launch, or are they withholding it for some reason?
Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
eklipse1 said:
I was abe to load the peru (SAM) version on my device with no problem, i am with WIND however but under networks i now have lte as an option as before i did not. i did not just download the kernal i download the stock firmware. do a factory rest after the odin process is done.
Click to expand...
Click to collapse
I was trying the Peru one for a while, but it kept hanging up during the bootup. The message was in a foreign language, but I'm assuming it was "initializing". It would initialize for about 3 minutes then an error message would pop up saying something is not responding.
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
eklipse1 said:
Did you try recovery factory reset right after Odin does the root and installs the files?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I have been trying to. When I flash the firmware in odin, it reinstalls the stock recovery mod. Right after flashing firmware, it won't go into recovery mode on the first boot (first does some android robot install thing, then boots up). I attempted to install the TWRP recovery directly after the firmware, and then booting directly into recovery to factory reset, but I'm still getting a boot loop.
Apra24 said:
You know what.. Me being a dumbass tried again to root it after restoring it to the mexican firmware, and now I have the same problem. And now the restore isn't working this time. Why did it work once and not again? Who knows? I just keep trying to factory reset and reflash the firmware, but I'm getting nothing but bootloops.
Click to expand...
Click to collapse
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Yorgo1982 said:
I think due of the lock. We are not free as b4 to flash anyrom. 2day im shipping my phone to samsung rooted lol how gr8 is that lol
Click to expand...
Click to collapse
do they know it's rooted/void? Or did you somehow not trigger the knox/warranty void switch? I may just have to do the same thing...
Related
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
tr10 said:
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
Click to expand...
Click to collapse
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
xBeerdroiDx said:
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
Click to expand...
Click to collapse
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
tr10 said:
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
Click to expand...
Click to collapse
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice, I have done that countless times. I'm hoping that it changes one of these times though.
I took your advice regarding re-flashing the image and ticking the bootloader update option, odin stated it was successful and auto-rebooted. I pulled the battery and tried to enter recovery, no cigar.
Perhaps try the Heimdall route: http://forum.xda-developers.com/showthread.php?t=2374441
When attempting to flash TWRP recovery, my phone says in the top right hand corner:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enabled
START [224, 1440]
SECURE CHECK FAIL: recovery
Don't know what that means.
I haven't tried the heimdall method yet, not sure if I wanna give it a shot because it seems a lot more complex only to accomplish the same thing odin would. I can imagine something is stopping odin from putting a bootloader, or kernel. That same thing would stop heimdall. But, I have no idea what I'm talking about. Waiting to hear more advice before I make the hole I dug deeper.
Thank you for your time guys.
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Febby said:
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
xBeerdroiDx said:
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Click to expand...
Click to collapse
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
tr10 said:
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
Click to expand...
Click to collapse
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Febby said:
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Aou said:
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Click to expand...
Click to collapse
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Febby said:
I actually considered switching to a ONE today.
Click to expand...
Click to collapse
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
Either way. Also, if one fails, try the other of course.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
I converted the .img to a .tar and I sadly had the same results =( Thank you for the idea though, definitely helped.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
Thank you, I attempted to reflash the stock kernel included in the MDL package. No avail. Same problem. Good advice though!
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
I just reflashed the stock kernel, no cigar =( It is very strange to me that I can't get the phone to respond to anything other than download mode. Especially considering that I odin'd to stock. I'm starting to think I made it worse by going back to stock after flashing slimbean's weekly update.
Thank you for your time guys, keep the ideas coming, I'm definitely trying to come up with my own ideas.
I have so far done the following:
Odin'd MDL, MDB, Stock Kernel, Stock Recovery (All through download mode, as I don't have access to recovery.)
I've also tried to odin TWRP but I fail in Odin since download mode blocks the illegal recovery.
Thank you again for your time.
tr10 said:
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Click to expand...
Click to collapse
Im not so sure how everyone just over looked this but the rom in that link is for the att S3. So you flashed an S3 rom to your S4.
D2att is the s3 for att.
Jflteatt is the att variant.
http://www.slimroms.net/index.php/downloads/all/viewcategory/620-jflteatt
Thats the correct link to weekly roms for slim rom for our device. your partitions might just be corrupted in case maybe having a jtag or using the pit file for MDL would fix? :/ im not an expert haha just observations.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------
xBeerdroiDx said:
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Click to expand...
Click to collapse
You sure? On the att one majority of devs dont post on the att htc one section but eather "HtC one" section since all roms work vice versa on that phone international roms > works on all models of the one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hi Guys,
This was my original FW:
AP: N900UBUBMI5
CP: N900UBUBMI2
CSC: N900UUBBMI2
Model: SM-N900 International version ( no carrier branding etc), FW version was from Uruguay
I flashed the wrong stock yesterday, and when I found the right one and tried to flash back it wouldn't work. I keep on getting a failed message in Odin in the system.img stage. Tried several different stock roms, tried to wipe data in recovery with no luck. Anyone know what I can do?
yoedba said:
Hi Guys,
This was my original FW:
AP: N900UBUBMI5
CP: N900UBUBMI2
CSC: N900UUBBMI2
Model: SM-N900 International version ( no carrier branding etc), FW version was from Uruguay
I flashed the wrong stock yesterday, and when I found the right one and tried to flash back it wouldn't work. I keep on getting a failed message in Odin in the system.img stage. Tried several different stock roms, tried to wipe data in recovery with no luck. Anyone know what I can do?
Click to expand...
Click to collapse
You have posted the same question twice: (original link) http://forum.xda-developers.com/showthread.php?t=2489935
I have provided you instructions with a process to ROOT, install TWRP and work with the appropriate ROM files to get things operational. You responded to my PM stating you already had a recovery ROM you tried but it still fails.
Unfortunately, I have a feeling your device is glitched which is why I recommended you follow each section and each step to the letter. I understand this is redundant steps as you would be ROOTING, installing TWRP and going through a similar process as before but it's what we call process of elimination with troubleshooting in case something happened during the ROOT or with the install of your TWRP software. I have provided you with the appropriate ROM file and TWRP files for your device which should hopefully do the trick but downloading them takes time as hotfile limits your download speed.
I'm being a bit direct but your situation is more of a troubleshooting matter which takes time and has no magical/quick answer. Rather than posting twice, please try what is suggested and respond with the outcome so we can further troubleshoot.
Thank you!
Hi,
I really do appriciate all your help but it seems something else is going on. Once you told me the first time I installed TWRP already and that didn't solve the problem. I always get stuck in odin in the flashing of the system.img. I already tried everything you said many times today but it didn't work
Maybe this phone is different than other phones.
yoedba said:
Hi,
I really do appriciate all your help but it seems something else is going on. Once you told me the first time I installed TWRP already and that didn't solve the problem. I always get stuck in odin in the flashing of the system.img. I already tried everything you said many times today but it didn't work
Maybe this phone is different than other phones.
Click to expand...
Click to collapse
I understand you have installed TWRP to try and do a recovery but this is what I'm saying... Maybe the ROOT went sideways and something is glitched in the device. If you follow my instructions which I provided via PM, this involves rooting the phone again, installing TWRP from scratch and going through each step as if it were a new device. It will take about 1 hour to do this process due to hotfile server speeds but once you've gone through this process, if it still hangs then another problem may be occurring. My thoughts are the ROOT itself or the TWRP recovery have become corrupt somehow causing you to get stuck during the flashing process.
Hope this helps!
cellrama said:
I understand you have installed TWRP to try and do a recovery but this is what I'm saying... Maybe the ROOT went sideways and something is glitched in the device. If you follow my instructions which I provided via PM, this involves rooting the phone again, installing TWRP from scratch and going through each step as if it were a new device. It will take about 1 hour to do this process due to hotfile server speeds but once you've gone through this process, if it still hangs then another problem may be occurring. My thoughts are the ROOT itself or the TWRP recovery have become correct somehow causing you to get stuck during the flashing process.
Hope this helps!
Click to expand...
Click to collapse
You might be right, but when I tried to root my device again I got into a boot loop. My phone doesn't have a operational operating system so the root wouldn't work it just boot looped. After that I re installed TWRP and proceeded but again failed in the same place...
yoedba said:
You might be right, but when I tried to root my device again I got into a boot loop. My phone doesn't have a operational operating system so the root wouldn't work it just boot looped. After that I re installed TWRP and proceeded but again failed in the same place...
Click to expand...
Click to collapse
OK, when you go into TWRP, from the touch base menus, click on format or wipe and within this menu, click on each option in a clockwise direction twice. This will wipe your device and hopefully come this time, you'll be able to ROOT the device again. Let us know how it works.
yoedba said:
You might be right, but when I tried to root my device again I got into a boot loop. My phone doesn't have a operational operating system so the root wouldn't work it just boot looped. After that I re installed TWRP and proceeded but again failed in the same place...
Click to expand...
Click to collapse
Issue has been resolved as indicated by OP in this thread: http://forum.xda-developers.com/showthread.php?p=46653062#post46653062
Hi, I started a thread needing help with my wifi but it has developed into not even being able to boot at all; it stops at the galaxy logo and either freezes or keeps booting. I have gone to the Odin page with all the different things to do and flashed the file to get back to the original rom but that is really where the trouble began. right now the only thing I can do with my phone is get into download mode, I can't even get into recovery. I have flashed a pit file that worked the first time but I don't know if that is part of the problem or not. Can someone please give me some directions, thanks
Also the phone won't boot at all unless hooked up to a power supply, the battery alone doesn't do anything.
nate39 said:
Hi, I started a thread needing help with my wifi but it has developed into not even being able to boot at all; it stops at the galaxy logo and either freezes or keeps booting. I have gone to the Odin page with all the different things to do and flashed the file to get back to the original rom but that is really where the trouble began. right now the only thing I can do with my phone is get into download mode, I can't even get into recovery. I have flashed a pit file that worked the first time but I don't know if that is part of the problem or not. Can someone please give me some directions, thanks
Click to expand...
Click to collapse
More info is needed. What firmware / bootloader are you on? Was it rooted? Did you have a custom recovery installed? What version of ODIN are you using?
StoneyJSG said:
More info is needed. Which GS3 do you have? What firmware / bootloader are you on? Was it rooted? Did you have a custom recovery installed? What version of ODIN are you using?
Right now, it sounds like you might need to use enewman17's ODIN debrick file.
Click to expand...
Click to collapse
It is the AT&T s4. To be honest I don't know what firmware I am on, it is the one the Odin page said to use if you want to go back to stock. I never rooted it. The bootloader would be whatever the latest update was for this phone. I can't get into it to tell you anymore. I am using ODIN 10, the latest one. thanks
Well I finally got into recovery and did a factory reset, now it boots into the AT&T white splash screen before it just turns off. I am also wondering if my battery just died for some reason?
nate39 said:
It is the AT&T s4. To be honest I don't know what firmware I am on, it is the one the Odin page said to use if you want to go back to stock. I never rooted it. The bootloader would be whatever the latest update was for this phone. I can't get into it to tell you anymore. I am using ODIN 10, the latest one. thanks
Click to expand...
Click to collapse
ODIN 10? Try using ODIN 3.09 and see if that helps. The latest update would be Android 4.4.4 NJ4 firmware. This link should help you, it will give you root with safe strap recovery though: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
I meant 3.10, I will try the older version. What file should I flash?
nate39 said:
I meant 3.10, I will try the older version. What file should I flash?
Click to expand...
Click to collapse
Check out the link I posted in my last post. It should help you get your phone fixed.
I have been there. I went to the very last option which seems to be what I need unless I am missing something.
Neither odin 3.09 or 3.10 will even flash any file now. it either says invalid md5 or fails when it attempts it.
Well, I finally got it to boot into android but it is flaky at best. It is android 4.3 instead of 4.4 where it was initially. The wifi still doesn't work and now the keyboard keeps crashing everytime I do something. The build is jss15j1337ucuemk2 which I know is older than I had before. Does this give anyone a better idea of what I need to do? If I can get a stable flash then can I flash a modem file to fix the wifi? I really need some direction, thanks
Turns out the battery was completely drained which was causing some of the boot problems, I don't now how that happened but I am charging it now.
Well after using odin 3.8* I got it to install some older firmware ending in mk2 rather than the nc1 or nf4 that I had before the trouble. After I got it to boot, I went back into download mode and flashed the modem file and now everything works execpt I had to force stop Samsung keyboard and use swype. I would like to upgrade my firmware but since for a couple of more weeks it won't have a sim card I can't upgrade OTA. For some reason Kies says that firmware upgrade and initialization isn't supported with this model which makes no sense to me. It also says my firmware is up to date
Does anyone know how to flash to the latest firmware without me going through this nightmare again? thanks
nate39 said:
Well after using odin 3.8* I got it to install some older firmware ending in mk2 rather than the nc1 or nf4 that I had before the trouble. After I got it to boot, I went back into download mode and flashed the modem file and now everything works execpt I had to force stop Samsung keyboard and use swype. I would like to upgrade my firmware but since for a couple of more weeks it won't have a sim card I can't upgrade OTA. For some reason Kies says that firmware upgrade and initialization isn't supported with this model which makes no sense to me. It also says my firmware is up to date
Does anyone know how to flash to the latest firmware without me going through this nightmare again? thanks
Click to expand...
Click to collapse
If I were in your shoes I'd flash the nb1 tar file in Odin, any vein should work. See this for the tar file http://forum.xda-developers.com/showthread.php?p=56453100. You can then ota to the latest firmware which is 4.4.4, nj4
Sent from my Nexus 9 using XDA Free mobile app
thanks, and as far as you know this doesn't mess wifi up?
nate39 said:
thanks, and as far as you know this doesn't mess wife up?
Click to expand...
Click to collapse
I assume you ment WiFi and not wife? Can't help you with the wife but Wi-Fi should work fine
Sent from my Nexus 9 using XDA Free mobile app
nate39 said:
Well after using odin 3.8* I got it to install some older firmware ending in mk2 rather than the nc1 or nf4 that I had before the trouble. After I got it to boot, I went back into download mode and flashed the modem file and now everything works execpt I had to force stop Samsung keyboard and use swype. I would like to upgrade my firmware but since for a couple of more weeks it won't have a sim card I can't upgrade OTA. For some reason Kies says that firmware upgrade and initialization isn't supported with this model which makes no sense to me. It also says my firmware is up to date
Does anyone know how to flash to the latest firmware without me going through this nightmare again? thanks
Click to expand...
Click to collapse
Download a firmaware for your region from sammobile and flash it via odin 3.10. It will solve most of your problems
Muthumbi said:
Download a firmaware for your region from sammobile and flash it via odin 3.10. It will solve most of your problems
Click to expand...
Click to collapse
Sammobile isn't going to have anything for the i337 unless you're on mdl
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sammobile isn't going to have anything for the i337 unless you're on mdl
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I agree. But google has basically all he needs. More so rapidgator
I haven't found anything from Samsung to download. If I flash a newer build, do I also need to flash a modem file and a bootloader or can I just flash the PDA? thanks for explaining this to me.
And can I do a dirty flash so I don't have to lose everything again?
well, now I see that there is no sound. so I guess I will have to flash again.
nate39 said:
well, now I see that there is no sound. so I guess I will have to flash again.
Click to expand...
Click to collapse
There's. Something I'm yet to understand. Did you finally manage to boot into recovery? If so, flash a custom recovery (I recommend philz touch recovery) then use it to make complete wipe.
Then boot into download mode and flash latest pda firmware in the compressed file you downloaded. Ps: make sure it's from your region.
May be if you provided me with your region I'd get you all the files required
Pokmemon Go/ Uninstalled Kingroot and derooted boot screen custom & gear icon on boot
Hi, so a while ago I tried using kingroot and installed it for a little bit and used root to uninstall some factory installed apps like amazon, etc. then when i decided i did not want root anymore. i used the kingroot app to remove root and then uninstalled the kingroot application.
then i downloaded a root checker app to see if i was rooted. i was not.
now whenever i boot up my phone it says samsung and then the word custom with a gear icon below it.
now when i tried the newest version of pokemon go version 0.37.0 it says it cannot run on my device cause apparently it thinks i am rooted.
is there anyway to solve this? other than a factory reset?
I don't think a factory reset would help either.
You'd have to delete every trace of root left on your device, and kingroot probably left some files behind.
Unless you can find them, the most sure method is to flash another ROM (stock) though Odin.
I believe a custom kernel would also work, or the stock boot.img of your current ROM.
GDReaper said:
I don't think a factory reset would help either.
You'd have to delete every trace of root left on your device, and kingroot probably left some files behind.
Unless you can find them, the most sure method is to flash another ROM (stock) though Odin.
I believe a custom kernel would also work, or the stock boot.img of your current ROM.
Click to expand...
Click to collapse
ok i have the sch i545 on verizon. which program do i use to find and delete the files tha kingroot may have left behind. also where do i get this "rom"?
Rhalium said:
ok i have the sch i545 on verizon. which program do i use to find and delete the files tha kingroot may have left behind. also where do i get this "rom"?
Click to expand...
Click to collapse
The ROM you can get from Sammobile. As for the files left behind, I don't know how kingroot handles those, but to access and delete them you would have to be rooted.
GDReaper said:
The ROM you can get from Sammobile. As for the files left behind, I don't know how kingroot handles those, but to access and delete them you would have to be rooted.
Click to expand...
Click to collapse
ok, i powered down the phone and held the power and volume up buttons to get into recovery mode and then i selected wipe cache partition. and then rebooted. it seems that has solved the custom and gear icon below on when it first boots up. cause now it shows samsung galaxy s4 which is correct. but when i try pokemon go 0.37.0 it still says this device or software is not supported what should i do now? i heard somewhere that you can use xposed framework module
GDReaper said:
The ROM you can get from Sammobile. As for the files left behind, I don't know how kingroot handles those, but to access and delete them you would have to be rooted.
Click to expand...
Click to collapse
ok this is weird. i hold power and vol.up button to get into recovery, then i see flash that says no order i think. then i wipe cache partion. then i power off and boot and the custom ans gear icon is no there its just says samsung galaxy s4 on boot like it supposed to. but then when i go into poke go version 0.37.0 it still wont let me play cause it think im rooted and then i power off and boot up again and there it is again. the custom word and then the gear icon below it. should i do a backup of my phone ans do a factory reset? will that solve it?
Rhalium said:
ok this is weird. i hold power and vol.up button to get into recovery, then i see flash that says no order i think. then i wipe cache partion. then i power off and boot and the custom ans gear icon is no there its just says samsung galaxy s4 on boot like it supposed to. but then when i go into poke go version 0.37.0 it still wont let me play cause it think im rooted and then i power off and boot up again and there it is again. the custom word and then the gear icon below it. should i do a backup of my phone ans do a factory reset? will that solve it?
Click to expand...
Click to collapse
I already told you that a factory reset does not unroot.
If you want to completely unroot, flash the stock ROM.
If you don't want that, downgrade to Pokémon version 0.35.
0.37 has not even been officially released yet. I mean, I don't even have it on the play store and it's the same for many others.
PS: Xposed also needs root.
GDReaper said:
I already told you that a factory reset does not unroot.
If you want to completely unroot, flash the stock ROM.
If you don't want that, downgrade to Pokémon version 0.35.
0.37 has not even been officially released yet. I mean, I don't even have it on the play store and it's the same for many others.
PS: Xposed also needs root.
Click to expand...
Click to collapse
ok thanks, and do i need a specific version of this stock rom? sorry am new to this rooting and rom and stock firmware and bootloader and such.
also it seems there pushing the new update out slowly. also i think the older versions will no longer work soon once the newwer update is firnly established.
Rhalium said:
ok thanks, and do i need a specific version of this stock rom? sorry am new to this rooting and rom and stock firmware and bootloader and such.
also it seems there pushing the new update out slowly. also i think the older versions will no longer work soon once the newwer update is firnly established.
Click to expand...
Click to collapse
You need one for your specific phone model (AT&T or Verizon I assume).
GDReaper said:
You need one for your specific phone model (AT&T or Verizon I assume).
Click to expand...
Click to collapse
yes my phone is verizon. do i need to hook up my phone to a computer in order to flash? will i lose all of the data on my phone when i flash the ROM to it?
Rhalium said:
yes my phone is verizon. do i need to hook up my phone to a computer in order to flash? will i lose all of the data on my phone when i flash the ROM to it?
Click to expand...
Click to collapse
Yes and yes.
GDReaper said:
Yes and yes.
Click to expand...
Click to collapse
ok how do i get the stock boot.img of my current rom? also dumb question, could you explain what a rom is? also is odin a program that i use on my laptop to flash the rom to my phone while it is connected to my laptop? also what is sammmobile? and if you say i should get a rom, is there a specific version of the rom that i should get? sorry for dumb questions.
GDReaper said:
I already told you that a factory reset does not unroot.
If you want to completely unroot, flash the stock ROM.
If you don't want that, downgrade to Pokémon version 0.35.
0.37 has not even been officially released yet. I mean, I don't even have it on the play store and it's the same for many others.
PS: Xposed also needs root.
Click to expand...
Click to collapse
ok now do you mean a firmware or rom? am i at the right place see screencap. also how large should these files be? i already have odin downloaded. i am using this guide: http://downloadstockrom.com/download-android-4-4-2-stock-rom-for-samsung-galaxy-s4-sch-i545-2.html
GDReaper said:
I don't think a factory reset would help either.
You'd have to delete every trace of root left on your device, and kingroot probably left some files behind.
Unless you can find them, the most sure method is to flash another ROM (stock) though Odin.
I believe a custom kernel would also work, or the stock boot.img of your current ROM.
Click to expand...
Click to collapse
http://smallbusiness.chron.com/use-odin-android-28504.html
this website says i need a pit file and a tar file. i already found the pit file here on xda which was a few megabytes and am downloading the tar file from the site seen in the screencap below. are these the correct files i should be using?
Rhalium said:
http://smallbusiness.chron.com/use-odin-android-28504.html
this website says i need a pit file and a tar file. i already found the pit file here on xda which was a few megabytes and am downloading the tar file from the site seen in the screencap below. are these the correct files i should be using?
Click to expand...
Click to collapse
You don't need a pit file. And if the files are wrong, the instalation will just fail.
If that's the firmware you had previously, then it's ok.
GDReaper said:
You don't need a pit file. And if the files are wrong, the instalation will just fail.
If that's the firmware you had previously, then it's ok.
Click to expand...
Click to collapse
ok so i just use the tar file i got from the rwilco12 website and use that with odin and my phone?
Rhalium said:
ok so i just use the tar file i got from the rwilco12 website and use that with odin and my phone?
Click to expand...
Click to collapse
Yes. But if the firmware is older than what you had on the phone (5.0 > 4.3) it may fail to flash.
GDReaper said:
Yes. But if the firmware is older than what you had on the phone (5.0 > 4.3) it may fail to flash.
Click to expand...
Click to collapse
ok when i bought the phone it was on 4.4.2 or something and then when i got it i soon updated it to 5.0. so now you are saying to use it with this? http://androidromupdate.com/2015/08...y-s4-sch-i545-ota-update-with-loads-of-fixes/
the 5.0 lollipop one right? also is there a diference between a stock firmware and a stock rom or are they the saem thing?
Rhalium said:
ok when i bought the phone it was on 4.4.2 or something and then when i got it i soon updated it to 5.0. so now you are saying to use it with this? http://androidromupdate.com/2015/08...y-s4-sch-i545-ota-update-with-loads-of-fixes/
the 5.0 lollipop one right? also is there a diference between a stock firmware and a stock rom or are they the saem thing?
Click to expand...
Click to collapse
Stock ROM and stock firmware is the same thing.
GDReaper said:
Stock ROM and stock firmware is the same thing.
Click to expand...
Click to collapse
Have you even looked at any of the linkes or screencaps ive included in these posts? so this is the tar file i should be using to put my s4 back to stock? it says may 21 2013. see screencap. i got it from that rwilco 12 site.
So after I flashed the stock rom back on the phone is functioning good and everything seems to be in order. However when i try to root it it gives me this error in odin http://prntscr.com/g3sml0 . Does anyone know why this is happening to my SM-G935U ???
Thanks for the help in advance
I still get secure check fail in odin for no reason at all
intramorph said:
I still get secure check fail in odin for no reason at all
Click to expand...
Click to collapse
It sounds like a bad download. I think you need the .tar file and not the tar.md5 file...
check and try again.
intramorph said:
So after I flashed the stock rom back on the phone is functioning good and everything seems to be in order. However when i try to root it it gives me this error in odin http://prntscr.com/g3sml0 . Does anyone know why this is happening to my SM-G935U ???
Thanks for the help in advance
Click to expand...
Click to collapse
I've tried rooting SM-G935U multiple times. The ENG boot image flashes fine in Odin but once it boots into the OS it reboots every 45-60 seconds. I never get to flash the root.bat
I'm thinking something has definitely changed. Others aren't reporting quite the same struggle I'm experiencing (at least not to the extent I have.) I just got this phone 2 weeks back. It came with Nougat.
Though I don't get any errors in Odin. Are you using the modified version?
KLit75 said:
I've tried rooting SM-G935U multiple times. The ENG boot image flashes fine in Odin but once it boots into the OS it reboots every 45-60 seconds. I never get to flash the root.bat
I'm thinking something has definitely changed. Others aren't reporting quite the same struggle I'm experiencing (at least not to the extent I have.) I just got this phone 2 weeks back. It came with Nougat.
Though I don't get any errors in Odin. Are you using the modified version?
Click to expand...
Click to collapse
No i'm using the original one from sam's mobile. I'm also on nougat. I had the same issue the first time i tried to root,got stuck in a reboot loop so i had to flash original firmware. After that my phone is working as intended but i get this error in odin now. Is there another way to root this device or am i out of luck xD
By modified version do you mean if it's a t-mobile device "for example" with the U firmware flashed? in that case no it's the original SM-G935U device.
TheOne741 said:
It sounds like a bad download. I think you need the .tar file and not the tar.md5 file...
check and try again.
Click to expand...
Click to collapse
Hi and where can i find the .tar file please. Forgive me for being such noob
intramorph said:
Hi and where can i find the .tar file please. Forgive me for being such noob
Click to expand...
Click to collapse
G935U Bootloader is locked
take a look here
https://
forum.xda-developers.com/sprint-s7-edge
intramorph said:
No i'm using the original one from sam's mobile. I'm also on nougat. I had the same issue the first time i tried to root,got stuck in a reboot loop so i had to flash original firmware. After that my phone is working as intended but i get this error in odin now. Is there another way to root this device or am i out of luck xD
By modified version do you mean if it's a t-mobile device "for example" with the U firmware flashed? in that case no it's the original SM-G935U device.
Click to expand...
Click to collapse
By modified I just meant the version of Odin youre using.
When you say you had to flash back to the original firmware, do you happen to know which version?
KLit75 said:
By modified I just meant the version of Odin youre using.
When you say you had to flash back to the original firmware, do you happen to know which version?
Click to expand...
Click to collapse
I do i used this one https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/TMK/download/G935UUES4BQG1/181625/
also i tried the modified version of odin as well as the latest. By now i've just given up. it's just not worth it imo
intramorph said:
I do i used this one https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/TMK/download/G935UUES4BQG1/181625/
also i tried the modified version of odin as well as the latest. By now i've just given up. it's just not worth it imo
Click to expand...
Click to collapse
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
KLit75 said:
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
Click to expand...
Click to collapse
It wasnt successful. It send me into a boot loop. Much like you. I couldn't run the root.bat file either. After that I just flashed original rom and that's it
Sent from my SM-G935U using Tapatalk
KLit75 said:
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
Click to expand...
Click to collapse
Hey man i was wondering if you still want to root. here's what worked for me. https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 . This method works for the sm-g935u. Also xposed works as well
The only thing i could find that was wrong was that my device was a bit laggy after rooting it but i gave it some time and it's lag-free now. I'm glad i did this. The downside is there's no custom recovery but maybe we'll get one soon. Good luck
intramorph said:
Hey man i was wondering if you still want to root. here's what worked for me. https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 . This method works for the sm-g935u. Also xposed works as well
The only thing i could find that was wrong was that my device was a bit laggy after rooting it but i gave it some time and it's lag-free now. I'm glad i did this. The downside is there's no custom recovery but maybe we'll get one soon. Good luck
Click to expand...
Click to collapse
I just rooted it Sunday night but thanks for letting me know!:good:
If you could though, please tell me which version of xposed you flashed. Was it the purify os v87 sdk24 from 7/26?
KLit75 said:
I just rooted it Sunday night but thanks for letting me know!:good:
If you could though, please tell me which version of xposed you flashed. Was it the purify os v87 sdk24 from 7/26?
Click to expand...
Click to collapse
it was purifyos and you flash the zip in Flashfire mount system