Database Users

[Q] Note 3 N900W8 soft bricked, backup not working.. can't find a compatible firmware

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...

[Q] Help a Noob please? Flashing the Stock ROM won't work

Hello, I am new to these forums as well as owning an Android device, and was directed here from Reddit when I posted my question there. to save time, I'll simply copy/paste my explanation of my predicament from Reddit, but if I seem to be leaving something out, please tell me so I can offer up as much information as I can.
"I've owned a Galaxy S5 for a little over 2 weeks, and for the past 4-5 Days, any time I try to Turn it on, I receive a message that says "Secure Fail: Modem", in red letters at the top left of the screen, and in the middle there is a yellow triangle with an exclamation point with the following text underneath "System software unauthorized by verizon has been detected on your device. please shut Down and go to the nearest verizon store" I'm 17, and currently staying at Governor's school, so I didn't have a ride until yesterday when my Dad and Uncle came to help me try to fix my phone. We went to the Verizon store, where they said that it looked at though I had tried to "root" the phone, which I haven't. My theory is that this is the result of a pokemon game I downloaded from the internet for an emulator. We Called tech support who couldn't help us, but after a little Research, I tried downloading Odin and flashing it with the Stock Rom, but every time I do that, I get the same Error message, regardless of whether I wipe the phone first, or Remove the sim card or whatever, so I don't know what I'm doing wrong and thought that maybe reddit could help me."
I've tried to flash the stock rom several times as per the following video: apparently I cannot link to outside content; however, the video is titled "How to Flash Stock Firmware for Galaxy S5 [All Variants] by Odin3" on youtube
if anyone could help me I would greatly appreciate it.

Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.

calishooter said:
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
Click to expand...
Click to collapse
I downloaded that file and ran it too, but it still gave me the same error message when the phone booted

Regelope said:
I downloaded that file and ran it too, but it still gave me the same error message when the phone booted
Click to expand...
Click to collapse
Restart your phone in recovery mode by shutting the phone down and then starting it back up by holding the home, volume up and the power keys until you see the blue text at the top of the phone saying recovery booting. When it boots into recovery use the volume key to select wipe cache partition and then press the power key to run that. Then select wipe data/factory reset and run that. When that's done select reboot system and see if it starts normally. If that doesn't work try Odin with the tar and pit file.

Misterxtc said:
Restart your phone in recovery mode by shutting the phone down and then starting it back up by holding the home, volume up and the power keys until you see the blue text at the top of the phone saying recovery booting. When it boots into recovery use the volume key to select wipe cache partition and then press the power key to run that. Then select wipe data/factory reset and run that. When that's done select reboot system and see if it starts normally. If that doesn't work try Odin with the tar and pit file.
Click to expand...
Click to collapse
I've tried all of that, even the pit file, it's still telling me that it detects system software unauthorized by verizon, and I don't know why or how it would if I've supposedly wiped the phone clear several times over

Regelope said:
I've tried all of that, even the pit file, it's still telling me that it detects system software unauthorized by verizon, and I don't know why or how it would if I've supposedly wiped the phone clear several times over
Click to expand...
Click to collapse
what model phone do you have? not sure why itd initially have said it but its possible you messed it up and possibly tripped knox or something for it to say that and not let you flash anything.. what apps besides thst game have you installed prior? were u rooted prior etc.
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
also whatd you do with this "pokemon" game i assume is a rom file for an emulator before this happened? what "emulator" were you using?
Sent from my SM-G900V using XDA Premium HD app

calishooter said:
Try using this guide to restore your phone. http://forum.xda-developers.com/showthread.php?t=2784880
I have no idea why your getting those errors. Somebody here will help you on that.
Click to expand...
Click to collapse
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Sent from my Kitkat CromiX TF700 tablet.

elliwigy said:
what model phone do you have? not sure why itd initially have said it but its possible you messed it up and possibly tripped knox or something for it to say that and not let you flash anything.. what apps besides thst game have you installed prior? were u rooted prior etc.
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
also whatd you do with this "pokemon" game i assume is a rom file for an emulator before this happened? what "emulator" were you using?
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
johnnytraveler said:
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Sent from my Kitkat CromiX TF700 tablet.
Click to expand...
Click to collapse
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.

Regelope said:
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Click to expand...
Click to collapse
Other than what I posted in the recovery thread and what I posted a few posts up that's pretty much it. You could try the nand erase all and efs clear options, check the screen shot and make sure your check boxes are correct. Also if you didn't download the files from the thread I posted I suggest you do. Honestly if none of what was already suggested doesn't work I would contact Samsung. I've had and seen your error before and successfully reset my phone before.
View attachment 2813604

Regelope said:
everything I downloaded was from the google play store, with the exception of the "pokemon emerald" rom from coolrom.com. I hadn't attempted to root the phone prior, I didn't even know what that meant until I googled the error message. that actually brought me to a thread on this site where somebody had tried to root their S3 and got the same message. as for the model of the phone, all I know is that it's an S5 and that I got it at Verizon.
I've done everything suggested to me multiple times, so If I can't figure something out by this afternoon, I'll try to get a hold of him.
Click to expand...
Click to collapse
i guess my question was how did you try to run the rom? its a long shot but thinkin since technically its a rom file maybe you used it wrong.. also, theres dev edition s5 and retail s5 for vzw so it does matter which model you have and which odin files youre trying to use.. since phone is less than a year old, id contact samsung if you cant get it fixed and theyll send you a return kit and reflash the software for you.. something similar happened to someone with an s5 active on att n samsungs gonna help him.. only reason he needs to send it in however is cuz there is no s5 active tar available yet for him to odin. you should b able to on yours but hard to fix without having the device in hand and u saying uve tried everything
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
i guess my question was how did you try to run the rom? its a long shot but thinkin since technically its a rom file maybe you used it wrong.. also, theres dev edition s5 and retail s5 for vzw so it does matter which model you have and which odin files youre trying to use.. since phone is less than a year old, id contact samsung if you cant get it fixed and theyll send you a return kit and reflash the software for you.. something similar happened to someone with an s5 active on att n samsungs gonna help him.. only reason he needs to send it in however is cuz there is no s5 active tar available yet for him to odin. you should b able to on yours but hard to fix without having the device in hand and u saying uve tried everything
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
I just downloaded it from the site I mentioned and opened it using the emulator I downloaded with google play.
how do I tell the difference between the dev and retail editions?
I'll see about contacting samsung, since I seemed to have bricked it.

Regelope said:
I just downloaded it from the site I mentioned and opened it using the emulator I downloaded with google play.
how do I tell the difference between the dev and retail editions?
I'll see about contacting samsung, since I seemed to have bricked it.
Click to expand...
Click to collapse
theres a soft brick (recoverable) and a hard brick (not recoverable).. normally a hard brick your phone wont come on or go into any mode at all.. soft brick is when it starts up but either bootloops or wont boot at all into the os (like yours).. im just lost as to why it wont work! crazy.. if u got at vzw and dont know what a dev edition is then u most likely have a retail s5 so mister odin guide should work..
Sent from my SM-G900V using XDA Premium HD app

johnnytraveler said:
I use this method and it worked great. I suggest you try it again, to include re downloading the tar file. Follow the straightforward instructions. Leave your phone connected to the computer even after you flash the tar. It will go through the whole reboot process while connected to the computer. If you still have problems, ask mrxtc (op). I see him all over the place and he seems pretty good at helping people fix problems.
Click to expand...
Click to collapse
Yea man it worked for me too. If you can get to stock recovery or Odin mode you should be able to do it. Factory reset and clear cache a whole bunch of times.

Just wanted to add I had the same error recently and tried everything. Nothing would fix

Seeing this twice in just a few days has me wondering if VZW has something buried in NK2 ...

I just registered because I'm having this same problem and haven't been able to solve it. I've never flashed any of my phones until last night, because of this error. I followed the instructions in Misterxtc's thread, but no dice. Still looking for help.

radicalXace said:
I just registered because I'm having this same problem and haven't been able to solve it. I've never flashed any of my phones until last night, because of this error. I followed the instructions in Misterxtc's thread, but no dice. Still looking for help.
Click to expand...
Click to collapse
Have you tried Kies to restore the phone to stock? Or even Verizon's Upgrade Tool (which also repairs)?

Rapunzl said:
Have you tried Kies to restore the phone to stock? Or even Verizon's Upgrade Tool (which also repairs)?
Click to expand...
Click to collapse
The only way I can do that is to get the phone to boot, which it will not get past the error stated in this thread: "SECURE FAIL: modem" I just tried to get all of that to work (sorry the late response was at work) and again it's a no go, I'm going to take it to Verizon, but I'm not optimistic about what kind of results I'm going to get there.
The phone came with the NI2 SW to begin with, and I tried to install that with Odin. gets me about half a second of the normal Samsung splash screen then straight back into the error, after that first boot, no splash only the error.
Thanks for the suggestions though.

radicalXace said:
The only way I can do that is to get the phone to boot, which it will not get past the error stated in this thread: "SECURE FAIL: modem" I just tried to get all of that to work (sorry the late response was at work) and again it's a no go, I'm going to take it to Verizon, but I'm not optimistic about what kind of results I'm going to get there.
The phone came with the NI2 SW to begin with, and I tried to install that with Odin. gets me about half a second of the normal Samsung splash screen then straight back into the error, after that first boot, no splash only the error.
Thanks for the suggestions though.
Click to expand...
Click to collapse
I couldn't even get my phone to start yesterday... just a black screen. I thought it was hard bricked. I did a chat with Samsung support, and they helped me recover in less than five minutes.

tr889 said:
Just wanted to add I had the same error recently and tried everything. Nothing would fix
Click to expand...
Click to collapse
I'm in the same boat. I've tried everything to get this issue resolved and I'm not having any luck.
Anyone know how I determine which tar file I should be using (NE9, NCG, etc)? I've got a SM-G900V and I think I've pretty much tried all of the tar files via this link - http://forum.xda-developers.com/showthread.php?t=2784880.

How To: Fix Lenovo A3000-H Soft Brick WITHOUT USB DEBUGGING OR CUSTOM RECOVERY

Can someone pls. help me. I have a rooted Lenovo IdeaTab A3000-H that accidentally got soft bricked after I edited build.prop on /system/build.prop
Info:
Model Number: Lenovo A3000-H
Android Version: 4.2.2
USB Debugging: Disabled
Currently Bootable To: Stock Recovery and Fastboot
(I could boot to ADB but it could only do sideload commands)
I have a recovery.img (CWM) that I can't flash since my PC can't detect my tablet while it's turned off
(And also if possible, can someone give me an original unmodded Lenovo A3000-H build.prop.bak and CWM flashable zip compatible for my tab.)

Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.

Droidriven said:
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Click to expand...
Click to collapse
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...

CEDoromal said:
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
Click to expand...
Click to collapse
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...

CEDoromal said:
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
Click to expand...
Click to collapse
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...

CEDoromal said:
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
Click to expand...
Click to collapse
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....

CEDoromal said:
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
Click to expand...
Click to collapse
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You nay have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )

CEDoromal said:
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
Click to expand...
Click to collapse
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)

CEDoromal said:
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
Click to expand...
Click to collapse
I don't think so but don't quote me, it'll either flash an succeed or fail, I doubt it will make things worse.
Have you looked at the possibility of using an extsdcard and a debrick.IMG or its equivalent to boot from a bootable extsdcard the same as PC does with a bootable USB? If it works on your device like it does some other devices you can boot into system from extsd and then do what you need to do to fix your device then return the sdcard to normal use after you are going again on its own.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?

CEDoromal said:
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
Click to expand...
Click to collapse
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)

CEDoromal said:
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
Click to expand...
Click to collapse
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.

Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA... >

Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA or a repair shop... >

Does anyone have the nougat update file

Hey guys i couldn't get in the beta so i was wondering if anyone has the Nougat update file that i can flash with odin.
Thanks

Join the club. No one has the VZW one for the flat s7 either....

Illogi.xbone said:
Join the club. No one has the VZW one for the flat s7 either....
Click to expand...
Click to collapse
Someone said they are going to try. I offered help if need be

billydroid said:
Someone said they are going to try. I offered help if need be
Click to expand...
Click to collapse
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.

jakemastaflash said:
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
Click to expand...
Click to collapse
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?

diego97yey said:
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
Click to expand...
Click to collapse
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.

jakemastaflash said:
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
Click to expand...
Click to collapse
Keep us posted man

Footer and verification error so far

Same here
Sent from my SM-G930P using XDA-Developers mobile app

dgr581 said:
Same here
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.

jakemastaflash said:
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
Click to expand...
Click to collapse
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.

vegoja said:
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
Click to expand...
Click to collapse
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!

jakemastaflash said:
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
Click to expand...
Click to collapse
Another update pull failed verification and resulted in another footer error. If installed without any modification it works, but after rooting and pulling the update.zip, trying to install it results in an error. It could be a security measure introduced to the update.zip to prevent installing on a phone without the matching signature assigned during the initial download.

Whenever i tried to follow the link it asked me for a security key ????

footer error
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian

N3ksta said:
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
Click to expand...
Click to collapse
I did not have my SD Card encrypted. I have also noticed some discrepancies between the update.zip I am extracting and the working VZW update.zip. Things like: the boot.img is 0kb, and there are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
I have tried extracting it in several different ways\environments and get problems with every pull.
Other variants are working on the same thing with the same issues. I have the last pull I made, but I can't continue working on this as heavily since I'm using my daily driver. I'll try again as new info\solutions come up.

Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Originally Posted by zimgir124
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named fota
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume down + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
After this it should update to the Android 7.0 beta and hopefully will be able to download future beta OTAs.
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again.
Click to expand...
Click to collapse

jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
So should this method work for us?

jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)

15jpenni said:
So should this method work for us?
Click to expand...
Click to collapse
Ideally it should. However, I have not been able to successfully reproduce the same results as installing the update file without modification.
---------- Post added at 09:04 PM ---------- Previous post was at 09:00 PM ----------
N3ksta said:
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
Click to expand...
Click to collapse
This is for the SM-G930P regular S7 (not edge). I have pulled it via filemanager app after full root, and via adb on linux and windows after eng kernel root and full root. All of them yielded an apropriately sized update.zip, but it seems to get corrupted during the rooting or extraction process.
Also, there may be a reason behind our update.zip not having a boot.img. We may not need a new boot.img after updating to PJ2, so it isnt packaged in our update. If someone can repackage the update.zip so it passes verification we may have more luck.

Stock bootoloader for Samsung Galaxy S7 SM-G930V

Hi community
I have a Samsung Galaxy S7 SM-G930V with Android 7.0. I tried to get root but first I had to unlock bootloader. I flashed the "Engineer Bootloader" (a file named Samsung_G930x_QC_Rooted_BOOT.TAR) with Odin for engineering bootloader and no problem then the phone reboot. There comes the problem, the phone is on a bootloop, it shows the screen "Samsung Galaxy S7" and restart again, over and over.
People suggest to go to recovery mode and wipe data and factory reset, I already did that but it didn't work.
I'm sure that flash the complete ROM again will solve the problem but the ROM is 2.50 GB and my Internet connection is very very slow so I can't download it. Maybe flashing just the custom boot.img the problem gets solved, can somebody bring me just that file? Please I need it really much.
Thank you very much.

From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.

dude, THANK YOU VERY MUCH!!! you saved my life. I don't understand why people post tutorials with wrong files. THANK YOU VERY MUCH AGAIN.

CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Wow... I have searched high an low for this. Thank you.

CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Is there a version of this that's just stock, no root or special engineering version?

ItsKipz said:
Is there a version of this that's just stock, no root or special engineering version?
Click to expand...
Click to collapse
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.

Scottie32583 said:
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Click to expand...
Click to collapse
This is what the file looks like I have...