Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
I am in the same boat. Please let me know if you get an unbrick image..
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Chay555 said:
I am in the same boat. Please let me know if you get an unbrick image..
Click to expand...
Click to collapse
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
Good news! I was able to get the phone booted up again. Bad News: Its back on Lollipop firmware (BP1.) So what I did was I used the files from jrkuses working root method 3/4/16 and flashed them through Odin. First I flashed the PB1 unbrick image in his OK3 file, then I flashed the Nk2 kernel also included in the OK3 file, and last I flashed a file called VZW_BPB1_KERNEL_ONLY.tar.md5 also in the folder. Flashing those got me booted back on 5.0 safely.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Chay555 said:
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
Click to expand...
Click to collapse
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
akaplo said:
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
Click to expand...
Click to collapse
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Chay555 said:
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Click to expand...
Click to collapse
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Nandr0idC0nsumer said:
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Click to expand...
Click to collapse
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Chay555 said:
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Click to expand...
Click to collapse
Reset using stock recovery. it usually takes about 20min on the vzw screen
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions. I have hard bricked my phone before I repaired it using win32img creator using an sd card. I never messed with partitions ever again after that.
akaplo said:
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Click to expand...
Click to collapse
stellar0322 said:
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions.
Click to expand...
Click to collapse
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
akaplo said:
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
Click to expand...
Click to collapse
Alright. I'm confused
EDIT: looked through the thread now. That's a hardbrick. Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Nandr0idC0nsumer said:
Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Click to expand...
Click to collapse
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
akaplo said:
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
Click to expand...
Click to collapse
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Nandr0idC0nsumer said:
Reset using stock recovery. it usually takes about 20min on the vzw screen
Click to expand...
Click to collapse
Is good now. Thank You
Chay555 said:
Is good now. Thank You
Click to expand...
Click to collapse
Congrats! You get a cookie.
Nandr0idC0nsumer said:
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Click to expand...
Click to collapse
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
akaplo said:
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
Click to expand...
Click to collapse
I've read up on the Snapdragon 80x boot ROMs, and there appears there is only 1 way to get into qhsusb_bulk mode, which is to have the bootloader corrupted and it is automatically triggered.
If it's not in that mode, it's a brick, go to Verizon and tell them it randomly died
there is nothing that can be done from now. good luck dealing with verizon/samsung and I hope you're still in warranty.
PD1 unbrick image.
https://www.androidfilehost.com/?fid=24562946973631519
Related
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
TwistedPoet said:
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
Click to expand...
Click to collapse
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
buhohitr said:
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
TwistedPoet said:
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
Click to expand...
Click to collapse
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
buhohitr said:
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
TwistedPoet said:
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
Click to expand...
Click to collapse
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
At last I got to know lot of things from this thread as I'm new to this trade.
TwistedPoet said:
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
Click to expand...
Click to collapse
Update - With some very helpful guides and a little but of explanation, I was able to return to stock ROM, which returned my ability to boot into recovery mode. I also successfully flashed Safe strap Recovery onto my device. After looking at the guide about which custom ROM's can be flashed onto the phone, I'm considering using one but I am a tad hesitant. I know very very little about framework, kernels and modules. So, I guess we'll see. Thanks for the simply excellent links and your time!!!!!
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
rleighska said:
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
Click to expand...
Click to collapse
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
recovery
rleighska said:
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
Click to expand...
Click to collapse
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
Iceburn1 said:
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Click to expand...
Click to collapse
Any help is appreciated!!! I have no idea what to do next. I've done and re-done everything possible. For whatever reason it won't let me boot into recovery. It just goes straight to the Samsung screen with the warranty bit kernel at the top. I just reflashed the stock firmware and it booted up to the samsung screen showing "recovery booting" and "set warranty bit : recovery" at the top. If I flash a recovery (through odin, the same way I flashed the firmware) it will boot to the same screen, but will say "set warranty bit: kernel" instead, but will not go past that screen. I've tried several recoveries, all of them take me to the same screen when flashed. I feel like I'm in a boot loop myself with the things that I've been trying to get this thing to work.
A friend of mine said when I'm at the point that I'm on the samsung screen with the "set warranty bit: kernel" I should be able to boot to download and flash a stock kernel through odin. I haven't found one kernel file that worked. Every one I've tried either gives a md5 binary error or makes odin freeze and close.
I don't think I was using ART. When I got the phone all I did was root it, didn't even get a good ROM on it yet, but then again, I'm not exactly sure what "ART" is because I'm not 100% familiar with all of the terminology just yet, but I'm learning (or trying to).
At this point all I want to do is get it back to stock and re-root it.
Or, if there was a way to reinstate my warranty with Sprint, I'd take it back to them and get a new one.
s5 fix
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Iceburn1 said:
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Click to expand...
Click to collapse
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
xposed installed or gravity?
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
Click to expand...
Click to collapse
I think I did have xposed installed and gravity come to think of it. I tried holding volume down and power and it went to the samsung screen with:
recovery booting.....
recovery is not seandroid enforcing
set warranty bit : recovery
If I turn off, go back to download mode, flash recovery, let it reboot, it will then still be stuck on the samsung screen, but will have:
set warranty bit: kernel
I have not yet found a kernel that will flash successfully and I can't get it to go into recovery at all, just download. It keeps getting stuck on the samsung screen with either the set warranty bit : recovery, until I flash recovery, then it says set warranty bit : kernel.
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Click to expand...
Click to collapse
I'm not sure if I was on ncb or nd2. How do I tell? When I got it I rooted it with CF- auto root, but I didn't do anything else to it that I can recall. I was going to install a rom, but the file wouldn't transfer for me, so I gave up on that until there were other roms to try. The only other thing I did once rooted was download titanium backup, did a backup of everything, downloaded xposed, and was using some of the modules from there. I was using twrp recovery and now I can't get anything to come up that even says twrp.
rleighska said:
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
Click to expand...
Click to collapse
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Nyc1231 said:
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Click to expand...
Click to collapse
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
safemode
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
rleighska said:
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
Click to expand...
Click to collapse
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Nyc1231 said:
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Click to expand...
Click to collapse
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
xposed and gravity
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Iceburn1 said:
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Click to expand...
Click to collapse
I can't get it to boot to recovery. When it starts it shows the kernel message at the top in yellow, the samsung logo etc. and will not move from that screen. The only other thing I can do is put it in download mode.
safe mode
Safe mode is different from download and recovery it boots you into phone so u can disable xposed or gravity lossiboy the cause
rleighska said:
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
Click to expand...
Click to collapse
Have you try using different version of odin when restoring to a stock firmware?
Sent from my SM-G900P using Tapatalk
Iceburn1 said:
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
Click to expand...
Click to collapse
I tried that and it still goes right to the samsung screen with
recovery booting.... in blue
set warranty bit : recovery in yellow
GAH! So how screwed am I? I can't even get into recovery. I'm non-dev, bootloader unlocked and rooted. I was going to restore the tether hack in order to take the new OTA. I accidentally deleted build.prop and rebooted.
I can't get into recover at all holding down volume down + PWR. I only get the unlocked bootloader warning and that is it. Phone shuts down. Since the phone is essentially off, my PC never recognizes it to allow me to use RSD.
Any thoughts, ideas, suggestions?
Thanks!
lkevinl said:
GAH! So how screwed am I? I can't even get into recovery. I'm non-dev, bootloader unlocked and rooted. I was going to restore the tether hack in order to take the new OTA. I accidentally deleted build.prop and rebooted.
I can't get into recover at all holding down volume down + PWR. I only get the unlocked bootloader warning and that is it. Phone shuts down. Since the phone is essentially off, my PC never recognizes it to allow me to use RSD.
Any thoughts, ideas, suggestions?
Thanks!
Click to expand...
Click to collapse
OK, I was able to get into stock recovery. I'm going to look for the 21.11.21 files...
Just reflash the appropriate FXZ making sure to use House of Moto's keep data option
asuhoops8628 said:
Just reflash the appropriate FXZ making sure to use House of Moto's keep data option
Click to expand...
Click to collapse
Wow, I'm an idiot!! Can't believe I did that. So, I downloaded the 4.4.4 21.11.21 ZIP and I used fastboot/mfastboot to flash the boot images and system image. I stopped and didn't erase my data because this is the exact version I'm running, only the build.prop is missing. This did the trick.
In order to help anyone else in a similar jam, I will try to post links to where I downloaded and the forum page with the instructions I followed, but they're on my laptop so I'll have to do it later.
Big sigh of relief... I've never seen an android device of mine in that bad state before!
Thanks for your input!
lkevinl said:
Wow, I'm an idiot!! Can't believe I did that. So, I downloaded the 4.4.4 21.11.21 ZIP and I used fastboot/mfastboot to flash the boot images and system image. I stopped and didn't erase my data because this is the exact version I'm running, only the build.prop is missing. This did the trick.
In order to help anyone else in a similar jam, I will try to post links to where I downloaded and the forum page with the instructions I followed, but they're on my laptop so I'll have to do it later.
Big sigh of relief... I've never seen an android device of mine in that bad state before!
Thanks for your input!
Click to expand...
Click to collapse
That works too! Glad you got it working
hello my phone wont boot past Moto logo. just stays there. how did you get yours into recovery please?
---------- Post added at 07:27 AM ---------- Previous post was at 07:25 AM ----------
lkevinl said:
OK, I was able to get into stock recovery. I'm going to look for the 21.11.21 files...
Click to expand...
Click to collapse
how did get into recovery from a boot loop?
Okay, so I'm having this problem where my phone get stucks in a bootloop when I flash back to stock.
The only way it gets out of bootloop, is if I install root. The problem is I'm trying to go back to stock firmware for now, but my phone refuses to get out of the Samsung logo every single time I try and run stock.
My guess is it might have something to do with the partition.
I notice when I'm doing a factory reset/wipe.
It has consistently said how it can't mount, and I'm guessing something is wrong with my partition, because I got the right firmware for my phone. It's N-902T.
If anyone has advice on this, I'd greatly appreciate it. Right now, I have no choice but to run a rooted phone until I figure out a way to get back to stock.
Ive never seen this before
[email protected] said:
Ive never seen this before
Click to expand...
Click to collapse
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Staying rooted is the best thing you can do did you flash the wrong firmware
Sent from my SM-N920T using Tapatalk
Anthony092 said:
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Click to expand...
Click to collapse
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
I'll try and do it and let you know how it goes.
Anthony092 said:
I'll try and do it and let you know how it goes.
Click to expand...
Click to collapse
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
Akw6190 said:
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Click to expand...
Click to collapse
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Anthony092 said:
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Click to expand...
Click to collapse
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------
Anthony092 said:
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Click to expand...
Click to collapse
In this case, use the method I posted above, but try re-downloading the latest firmware for your device from sammobile.com and flash that. It should overwrite all of your partitions and then simply require a factory reset from stock recovery to boot. If that doesn't work, you may need to flash the PIT file for your device, which I'm sure can be found somewhere around here. I'm not sure the exact method to do that, however.
Akw6190 said:
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
Click to expand...
Click to collapse
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Akw6190 said:
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Click to expand...
Click to collapse
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Anthony092 said:
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Click to expand...
Click to collapse
You too, buddy. If you figure it out, report back and let us know. It may help someone in the future.
guaneet said:
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Click to expand...
Click to collapse
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Anthony092 said:
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Click to expand...
Click to collapse
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
guaneet said:
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
Click to expand...
Click to collapse
Thank you, very much appreciated it. I'll download from there instead =)
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Jammol said:
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I was flashing N902TUVU2COI5, however I'm going to try and flash the latest firmware and see how it goes.
Unfortunately, I haven't found anything exactly telling me how to the pit file, so I'm for now going to stay away from that...just waiting for the latest firmware to download and I'll flash it and post my results.