Database Users

I think I'm bricked.

I've had my fascinate for about 3 weeks and I rooted it and overclocked. I flashed a 2.2 rom that was for a I9000 because my buddy said it worked on his captivate. When it come back on after reboot the screen said galaxy s I9000 and that's it it just kept running that and nothing else. I could get into factory recovery but I can't do anything from there except reboot. and it won't flash update zip either. I will go into download mode and I tryed odin restore now it just has samsung across the screen. Am I bricked cuz I can't get anything to work?

Oh now I've manage to get into CWM recovery but it won't let me apply any zip files or restore any back ups, is that vodoo messing things up?

So you flashed a ROM that isn't compatible with your phone? And you are suprised that it broke?
As for downgrading you might try to find the stock image via: hxxp://forum.xda-developers.com/showthread.php?t=782204&highlight=odin
If that doesn't work you better figure out a good excuse for the Verizon store...
Good luck!

frostysax said:
Oh now I've manage to get into CWM recovery but it won't let me apply any zip files or restore any back ups, is that vodoo messing things up?
Click to expand...
Click to collapse
Were you running a kernel with Voodoo installed and active when you flashed the ROM?
If you're filesystem is still ext4 and you don't have a Voodoo kernel running, I'm thinking you've got a date with Odin at best.
Sent from my SCH-I500 using XDA App

Odin. I would like to think you should be able to remove it via the uninstaller listed on that page as well, ?if it is voodoo, but if you can't install anything with CWM then I know it won't work. :/ Also, did you disable voodoo first?
He was valid in trying something different... I don't believe using a ROM from another phone entirely was a good idea, but eh, now we know for sure not to do it.

Yes gentlemen I think its bricked. I have tried the odin restore, I have put the stock image on the SD card using my htc eris and put it in CWM/backup and then put the card back in the phone and tried a backup/restore it still comes up can't mount data every time it says E:Can't mount /dev/block mmcblk0p2(File exist) Can't mount data . I really don't think there's anything left for me to try fellas. I just got my service put back on the eris. If I can't get into it you can't prove its been rooted can you I still got a week left before my 30 days is up. I some wan't to experament with any solutions I am wide open before I put this in the mailbox and send it back. Thanks for your help guys but I will get me another, I guess you know what not to do now"LOL"

frostysax said:
Yes gentlemen I think its bricked. I have tried the odin restore, I have put the stock image on the SD card using my htc eris and put it in CWM/backup and then put the card back in the phone and tried a backup/restore it still comes up can't mount data every time it says E:Can't mount /dev/block mmcblk0p2(File exist) Can't mount data . I really don't think there's anything left for me to try fellas. I just got my service put back on the eris. If I can't get into it you can't prove its been rooted can you I still got a week left before my 30 days is up. I some wan't to experament with any solutions I am wide open before I put this in the mailbox and send it back. Thanks for your help guys but I will get me another, I guess you know what not to do now"LOL"
Click to expand...
Click to collapse
Oh wells... Sorry dude. Did you flash System, kernal and pit with Odin?

yes I did but nothing happened when I went to the pit file. Itook it out of m downloads put it in odin with the pit button and hit start,am I doing that right thats the only thing that I did'nt see anthing happen when I hit start. How do you fun the pit file in odin?

I ran into the same exact issue on day 1 with my Fascinate, minus flashing a ROM meant for another phone. I could boot, but my phone wiped to factory at every boot, and I couldn't even run the ota. I exchanged it that same day, and no troubles since. Good luck.
Sent from my Fascinate using the XDA app

you flashed your radio...it's bye bye... Go to verizon and try to blame it on the ota after you flash back to stock...
If you don't know what your doing.... dont do it... That is the number one rule in flashing roms....

Ya well I guess its an expensive paperweight now.I will take your advise and blame it on the OTA. I odered this one over the phone so they have to mail me another one no matter what. You live and learn and that was a great lesson on what never to do. Thanks for all your help I still have my eris to play with for now,I'm running nonsensikal froyo. Perhaps I will zip a new rom on that"LOL"

frostysax said:
Ya well I guess its an expensive paperweight now.I will take your advise and blame it on the OTA. I odered this one over the phone so they have to mail me another one no matter what. You live and learn and that was a great lesson on what never to do. Thanks for all your help I still have my eris to play with for now,I'm running nonsensikal froyo. Perhaps I will zip a new rom on that"LOL"
Click to expand...
Click to collapse
1: If you're going to mod your phone, you should have insurance, and be prepared to use it.
2: "Blaming it on the ota" just makes everyone suffer. You think that $600 phone will just pay for itself? Not likely. Consumers end up footing the bill, every time. And, in turn, companies like Motorola place E-fuses in their phones to prevent this very thing from happening to cover their bottom line, which in turn affects the modding community too by reducing access to devices.
3: Those phones do get tested when returned. They can/will see that it doesn't have proper software in it when they go to refurb it. And they have no problem charging your account for an out-of-warranty exchange after the fact.

Normally I would agree.... but...
1.they charge 600 dollars for a phone that is not worth 600.
2. There wouldn't be a problem if they didn't hold back the release of a new ota. (With a new update these phones are easily fixable.)
3. They over charge cellphone service. And add 300 dollar cancellation fees.... come-on they don't mind screwing us... screw them.
Sent from my SCH-I500 using XDA App

There is no excuse for fraud. This is 100% user error. Own up and pay for your choice to ignore the big warning at the top of every flashing thread.
Sent from my Voodoo-powered Fascinate with XDA

Are you serious. I just paid AT&T $300 dollars to cancel an expensive contract just to go to verizon and end up paying more. If you think the phone company is suffering you are sadly mistaken my friend. I have two phones on my contract and pay right at $250 a month, they ain't hurtin for money. I tell you what, if you bricked your phone and it was within your 30 days, now be honest would you call them and say hay I just voided my warrenty and I need to pay for this phone and give you more money for another one or would you try and come up with something else to say. It could happen to you

I do not believe you are bricked. Follow all instructions for odin and also fix the mbr using original.mbr or the program provided by adrynalyne.

Ethics aside, flashing a rom should not brick your phone. Unless you used Odin, and pushed the "radio" button, it can be fixed. Adrynalyne's voodoo removal fix should fix almost any phone problem. http://forum.xda-developers.com/showthread.php?t=804784
Try it and see if it works.

what is "mbr "I have not tried that yet and where would I find info on it? What roll does the pit file play in odin restore? is there a certain way to do the pit file? Everything flashed but when I got to the pit file put in odin and hit start nothing happens is that normal? Anymore feedback I will anything at this point, Thanx guys,

Pit is for partition mapping. Mbr is master boot record. From what I saw in one of your earlier posts it looks like your mbr is messed up. Use adrynalynes guide in the post linked to you above by Sgtmack.

I went to the above web site and downloaded the stock kernal but when Iwent to download the mbr file it sent me to a web page with almost nothing on it. again I ask when I do the pit file in odin can someone give me step by step cuz I feel like I 'm doing something wrong here.

flash write failure

Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?

Try flashing the factory image without using a tool kit. Google nexus 4 factory image. Download it to your pc and extract it. Run the flash-all.bat you'll find in there.
Sent from my Nexus 5

r4ff0r said:
Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?
Click to expand...
Click to collapse
Some Partitions of the phone have got some bad blocks causing it to act in such a way !! Seems RMA(if available) is the best recourse since there is no definative solution to this problem !! You can try hard reboot as well as someone once pointed out that his n4 magically restored during it but others dint have that much of luck !! Also u could give LGNPST a try but since that also writes the partition it is highly unlikely to get you through !! One Solution I know will surely work is Qualcomm PST using the HighSpeed USB Device . But unfortunately we need an expert help, probably a Qualcomm employee to get in touch with since the tool has still not been cracked by anyone for n4 though I read somewhere that someone was able to restore using QPST !! Also mostly a JTAG Repair can help you but thats a rip off !! I'll anyday prefer a official LG/Google Repair over a JTAG !!
Hope you find my post useful !!

THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/

r4ff0r said:
THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/
Click to expand...
Click to collapse
I was afraid of that. Try one thing. Relock the bootloader, fastboot oem lock, then re-boot and see if the bootloader locks. If it doesn't, and it probably won't, then rma is your option.
Edit, haha, I just read that thread you posted and they tried the same thing
Sent from my Nexus 5

i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.

r4ff0r said:
i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.
Click to expand...
Click to collapse
Google seems to have been pretty good with rma's when it's a hardware failure. Pretty sure your emmc is borked. But you never know until you send it in. Hopefully there won't be a problem.
Sent from my Nexus 5

Ok I'll give it a try on monday. But as far as i know, i'll need to call them first.
I could imagine that they'll try to let me wipe my data or give me any kind of instructions to see if they can resolve the problem right away? What do i tell them?
At latest when they'll lead me to the recovery i'll get stuck using TWRP at latest.
Any kind of conversation dialogue i can follow up?

Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5

Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time

jd1639 said:
Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5
Click to expand...
Click to collapse
It won't let you flash that either to the best of my knowledge !! Just don't tell those operators that you have unlocked your bootloader and have a custom recovery !! Basically they won't tell u to go into stock recovery !! They'll just ask you hard reset the phone using physical keys !! Bdw check my pm !!

r4ff0r said:
Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time
Click to expand...
Click to collapse
Np, not sure what to tell them. It still boots I assume so you can't tell them it won't boot. I guess just the truth, it is a developer phone after all so it should be flashable
Sent from my Nexus 5

Potential To Recover Note 4 Bootloader After Flashing Retail Firmware

***Updated: 04/09/2015
First, thank you BeansTown106 and ryanbg for previously sharing the information and technical expertise that has led to successful development of the "tool" that ultimately provides the means to recover a locked bootloader on the Note 4 Developer Device. Without your help and expertise this "tool" may never have been developed.
UDATE: 04/09/2015---There is now a step by step guide that will take you through a process that produces a flashable aboot recovery file for the Developer Edition bootloader if it becomes locked (by flashing retail firmware for instance). This backup MUST be done BEFORE your bootloader becomes corrupted and locked. It is strongly recommended that if you own a Developer Edition Note 4 that you take the time to make a backup of your aboot. This link will take you to a step by step process with links to the couple of files you will need.: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911. Thank you radionerd for the guide and again to BeansTown106 and ryanbg.
Most of us have heard or read about Developer Edition owners of the S4 or S5 that inadvertedly flashed a retail firmware or ROM that was not intended (safe) for the Developer Edition consequently turning their Developer Edition phone into a retail edition phone...locked bootloader. I want to emphasize that this method of recovering a Developer Edition bootloader has been tested and has recovered several Note 4 DE devices whose bootloaders were locked (purposely or inadvertently).

I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.

tfly212 said:
I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.
Click to expand...
Click to collapse
Yep, I don't understand either, but it happens.

jpcalhoun said:
Yep, I don't understand either, but it happens.
Click to expand...
Click to collapse
Yeah my Dev edition note 3 got ruined with running "nvbackup" so as a last resort i purposely flashed a retail rom hoping that would just make it work even though it would be locked...

This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.

gatesjunior said:
This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.
Click to expand...
Click to collapse
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?

mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Well, that's kind of my whole point I was being a little sarcastic. With a locked bootloader, lets just say Read-Only, you cannot really overwrite something RO that has already been loaded per say... You would have to be able to fastboot, from my experience, in order to be able to do that. Now if they are signing it, if we could somehow impersonate the key and resign with a newer version number that might work, because they probably have allowances for signed updates.
To me, that might be the only way of resolving this whole locked bootloader issue in general. They obviously have the ability to update them, so we need to figure out how to sign it somehow and or understand their conditions. Meaning, what if they are already planning the next planned bootloader version coming within the existing one. So in this case, if it doesn't match what is expected on the check it will fail along with the fact the signature is not correct.

mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Have you tried it from the phone useing Terminal Emulator and the su command?

I could only copy aboot.bak via terminal emulator. I couldn't get through with CMD in windows 7. (I have only copied the file.)

It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.

droidstyle said:
It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.
Click to expand...
Click to collapse
Not all have given up yet ... I am still hard at it.. Ye of little faith..

If anyone wants to send me an image of their aboot for research purposes, it'd make my day

ryanbg said:
If anyone wants to send me an image of their aboot for research purposes, it'd make my day
Click to expand...
Click to collapse
PM sent

wy1d said:
PM sent
Click to expand...
Click to collapse
anyway i can one too/??

larrycjr said:
anyway i can one too/??
Click to expand...
Click to collapse
I'm not certain that p6 is the aboot. I'm thinking it may be p7. I've asked for verification in the other thread.

is there an odin file for the developer edition device? if so will someone direct me there??

larrycjr said:
is there an odin file for the developer edition device? if so will someone direct me there??
Click to expand...
Click to collapse
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.

wy1d said:
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.
Click to expand...
Click to collapse
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.

gatesjunior said:
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.
Click to expand...
Click to collapse
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.

wy1d said:
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.
Click to expand...
Click to collapse
Well....... I would say you covered all the bases... lol

Is this it, is this the root for retail we have been waiting for, maybe?

ok, this method does not work - there was an attempt to flash a rooted system.img.ext4 image from a developer edition to a retail, it failed... with the exception of the members of this forum who verified that this method did not / does not work (thanks to all) the following set of instructions does not work...
again, sorry -
Note: I am not responsible for anything that might happen to your device. Please make a backup if possible or please make sure you know how to restore your phone back to factory using the correct stock roms. This Note 4 Developer forum does have resources to do so. Before proceeding below, please ensure you have tried to restore from stock roms via ODIN 3.09 (or correct version), as it may be the only way to recover your device.
The post here suggests (but untested / verified on a retail Verizon Note 4 NJ5) that a system.img.ext4 image, with root (Super SU), can be flashed using ODIN 3.09 to a retail device. I ask more experienced developers to try this first, and post your responses here. I will cite / note the steps which I have done below. I really hope other developers assist in the verification process - let me know if this works or not. I will pull this post if in fact this process fails
Using EFS Professional v2.1.80 Beta and a Verizon Note 4 Developer Edition SM-N910V, on the 4.4.4 version N910VVRU1ANJ5, did the following.
0. Restored the SM-N910V (Developer) to near stock - the only thing different was the recovery partition which had been previously flashed to TWRP
1. Downloaded UPDATE-SuperSU-v2.16.zip from this post (also where TWRP came from), and with my Note 4 connected to a PC, copied the zip file to the phone; rebooted into recovery, flashed Super SU with TWRP. Now it's rooted, right? restarted phone. Installed Busybox (required by EFS Professional), prompted me for root access, permission granted. Busybox ran. Good.
2. - instruction no longer available...
3. Using TWRP, reflashed my phone back to stock before root. Used ODIN 3.09 with my phone in download mode, flashed the SM-N910V_2015130_0116.tar back to my Developer edition, performed a factory reset, rebooted, did a minimal phone setup (bailed out of setup when I could) but Used the busybox.apk (stericson) to test root; installed it using the unknown resources option, ran it, it asked for root, I assume this was a sign that the ODIN flash went well and root held...
So, what remains - asking the developer community to test flashing the SM-N910V_2015130_0116.tar on a retail device using ODIN AP Mode, I do not have one to test...
Here is what I'm hoping for. That the SM-N910V_2015130_0116.tar can be successfully flashed to a retail device, which will then be fortified with root, yes. Maybe that can lead to the "promised land" where a developer, again - more talented than me, can find a weakness in the retail version, from within, to obtain root by other means; unless what I have done, is it!! If it is. Excellent...
If this does work on a retail verizon Note 4 (NJ5), excellent, glad to have helped. If there is a bounty due, ok, I suppose I could accept but not expecting it. I am more excited to give back to the community who has so given their precious time / resources... and so it goes...
Again, please let me know if this worked. I will down this thread immediately if it is detrimental to devices...
Rob

Bump for our possible savior!
Sent from my Note 4.

thanks
Subiegsr said:
Bump for our possible savior!
Sent from my Note 4.
Click to expand...
Click to collapse
Well, thanks, but not yet... And I'm just a measly Note 4 user who spent 700 bones on a device, had some willingness to try something different. actually, it was more common, right? I have seen other developers like beanstown106 (Nathan) and hsbadr do similar, in just handing us a pre-rooted system image only. Hey, if it's a minimum, great - it's a start. I cannot really take credit in that sense, but thanks for the sentiment just the same... greatly appreciated.
We really have to hope that the system.img.ext4 in that flashable package can be put onto a retail - let the games begin (keeping fingers crossed..)
thanks

Any testers yet? I will later today if no one tries before me.
Sent from my SM-N910V using XDA Free mobile app

This won't work. The reason it went okay on your device is because it's a DE with an unlocked bootloader. On retail, it won't boot.

bobbarker2 said:
This won't work. The reason it went okay on your device is because it's a DE with an unlocked bootloader. On retail, it won't boot.
Click to expand...
Click to collapse
ok, that's what we need to find out. what about the image will the retail edition not like?
comment - I remember flashing different modems on a locked note 3, that worked but at the same time I do remember flashing different boot or recovery on a note 3 and it not starting ( validating your claim here... ) - would it be like that experience?
here was my thinking:
1. the worst that'd happen is, yes the phone won't start, but not a brick per se, as Samsung unit's are pretty resilient, and a re-odin of the original system.img.ext4 ( belonging to the retail ed. ) can be easily restored, right?
2. this is an Identical version that goes on both phones, and correct me if I am wrong but the system partition can be flashed on both ( getting that sense looking at hsbadr's thread - to be clear, not that he said it would, he has not indicated that in any post, just my interpretation of what is flashed between the two phones )
lastly, if in fact it does not work, I will simply pull / close this post - with a final comment / statement and we move on.
thanks for your information, this is what we need to know...

anticloud said:
ok, that's what we need to find out. what about the image will the retail edition not like?
comment - I remember flashing different modems on a locked note 3, that worked but at the same time I do remember flashing different boot or recovery on a note 3 and it not starting ( validating your claim here... ) - would it be like that experience?
here was my thinking:
1. the worst that'd happen is, yes the phone won't start, but not a brick per se, as Samsung unit's are pretty resilient, and a re-odin of the original system.img.ext4 ( belonging to the retail ed. ) can be easily restored, right?
2. this is an Identical version that goes on both phones, and correct me if I am wrong but the system partition can be flashed on both ( getting that sense looking at hsbadr's thread - to be clear, not that he said it would, he has not indicated that in any post, just my interpretation of what is flashed between the two phones )
lastly, if in fact it does not work, I will simply pull / close this post - with a final comment / statement and we move on.
thanks for your information, this is what we need to know...
Click to expand...
Click to collapse
As bobbarker2 said two posts above it worked for you because you have a unlocked DE device. Authorization fails without the proper signature on the retail phone. This can only be attained from Samsung or Verizon. Thanks for trying but it's a no go.
EDIT: Yes, I did try to flash it on the retail version.

thanks.
howellcp said:
Any testers yet? I will later today if no one tries before me.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I saw bobbarker2's comment - thinking it won't work. I'd say, as long as you can reflash / recover your phone back to normal / working condition, go for it. My comment to bobbarker2 was that this may be worth a shot. I'd try it as long as I had a way to recover. I am not thinking this will lock a phone or anything like that, just make it not boot, like he claims, and a recovery of what should be on the phone will make it right...
Like I suggested to bobbarker2 - I am thinking this would flash and possibly boot (be ok) as it is just the system image, not any other file, and more so, I think it's the same system that goes on the retail and the developer. I am not knowledgeable enough to know yet (some might think dangerous enough) for sure, but just the same that's why I asked someone who has more knowledge than I, and I suspect you and bobbarker2 are better suited than I to know, plus, if it were that easy, it'd already be done this way, right? or is it the case where not too many people have a both a retail and a developer edition to find out on their own, it's a medium but recoverable risk.
just my two cents - proceed with caution.

The file won't flash. It gives an auth error in Odin.

gotcha.
Misterxtc said:
As bobbarker2 said two posts above it worked for you because you have a unlocked DE device. Authorization fails without the proper signature on the retail phone. This can only be attained from Samsung or Verizon. Thanks for trying but it's a no go.
Click to expand...
Click to collapse
ok, thanks - now I know, all in favor of closing this set of posts?
I will also pull the download too, to be safe.

ok.
WarlockLord said:
The file won't flash. It gives an auth error in Odin.
Click to expand...
Click to collapse
now I know.
thanks
sorry guys, chalk one up for too much knowledge not enough experience (referring to me )

anticloud said:
now I know.
thanks
sorry guys, chalk one up for too much knowledge not enough experience (referring to me )
Click to expand...
Click to collapse
No need to be sorry, thanks for trying.

SM-S727VL Root and Recovery

I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to nougat.

Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.

djared704 said:
Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.
Click to expand...
Click to collapse
Well that figures, im willing to use my device to work at it if anyone knows where to start.

I have 3 of these... not a noob but not an expert...say Pre-elite lol. I'm wanting to learn how to go further than use everybody else's solutions to root my phone's if somebody can give me some advice as to where to start as in I know how to root put it that way I was one of the people back in the day with the Evo when it was actually difficult no worries most of them were fine but these files we keep flashing these ROMs these kernels these firmwares where does one start when a phone like this 727 VL is obscure supposedly and nobody is doing anything to be able to root them I have everything that I need I'm sure and if I don't get it. It's somebody point me to a person or in the right direction to get started on what I need to due to learn how to write for I mean what where's the first step on these I've always just use everybody else's files. If that even makes any sense to anybody and anybody can give me a hand or show me the right way I'd be willing to do the work from there on I just need somebody to stick up a finger and say go there.... I mean if we have a twrp written, and we have OEM unlock, then why can't one of us do this I've been around long enough I've read long enough I've never once posted in these forms but I've read them daily... I know I got the skills I just need to know which ones to use. Odin fails like he said, fastboot for some reason still won't recognize, I actually made it one step with one of mine but it has to be a little incorrect because the only thing noticeable is it pops up with vo LTE at the top instead of just regular LTE like this one I'm on now. I was able to flash it with Odin believe it or not with what seems to be possibly just stock S727VLUDU2AQG1_ENG_boot_boxwares.tar
BUT the point is I was able to flash it with Odin and also it did change something because my phone now says there's been unauthorized changes and it wants me to restart it all the time so it can correct itself however it does not, it stays whatever it is, yes I know this is pretty vague however I got to the point where I just started trying anything on one of these phones to see if I could get any kind of anything to work and it did.. kind of.
I will say the USB drivers that's you find every where now do not work you have to go back to looks like version 1.5.5 1.0 SAMSUNG-USB-Driver-for-Mobile-Phones-15510.
With these drivers fast boots if I remember correctly will recognize it when you do fastboot devices however it still hangs on waiting on device. I'm sure I got more information my brains just a little foggy at the moment it is like 3 in the morning and I hope I didn't break any rules posting.
I did try flashing from SD card with no success yet nothing at all just error after error. I have tried twrp however it's supposed to be for this 727 VL I'm sure it's the same one everybody's got because it's only in one place that I've found but it comes up twrp-3.2.1-j7popqltefnvzw-201 and it will not flash.
I realize I have been pretty obscure however there's no reason why if all 5 of us with this VL stick together we can't get it rooted because I'm not going to give up LOL

Keep up the good work
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW

twrp
[email protected] said:
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW
Click to expand...
Click to collapse
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.

Masterx4020 said:
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.
Click to expand...
Click to collapse
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.

Justin1198 said:
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.
Click to expand...
Click to collapse
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.

Masterx4020 said:
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.
Click to expand...
Click to collapse
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632

Justin1198 said:
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632
Click to expand...
Click to collapse
Is there a way to tell if the bootloader is locked? (Sorry if I am asking noobish questions. I am just trying to learn.)

You can tell the Bootloader is locked because you get “Secure Check Failed” if you try to flash anything that has been modified. For example; The TWRP recovery file. We need root to bypass the Bootloader.

Allow

allow what
I feel like you're telling me to do something that's way over my head cuz I do not understand what do you mean by allow

I have read write access to root files now !!
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan

You can send them to me if you like.

No problem how do I not familiar with these forms
josh0426 said:
You can send them to me if you like.
Click to expand...
Click to collapse
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do

Pre-Elite said:
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do
Click to expand...
Click to collapse
[email protected]

Pre-Elite said:
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan
Click to expand...
Click to collapse
Can you please share the method that you used to gain read/write access? If you indeed have temp access, I can make it permanent also what firmware build are you on?

Absolutely
I'm not home right now but I'm headed there I'll be there in a couple hours I can if somebody wants to give you their email or email me because I can't post links or anyting I have the file that I used the wrong and I have the driver for Samsung for Odin that I used which I think I've mentioned in my original or previous post and by the way it is not temporary. This is permanent. I did a factory reset and it stays. I just need to know which permissions which file to go to to get my Superuser installed because it's still will not let me install that. But email me or tell me how to send it on here or something that way I can let you guys know or give you guys what I got. I'll tell you this I did not flash it with a v l ROM. I flashed it using a Verizon ROM the only thing that didn't work was my wife I which I think I originally and said back when I made my first comment on this thread I haven't done anything else I set my phone down and it was done clear back there I just didn't realize it. But it is not a VL ROM it's a Verizon ROM a v not a straight talk and my wife I would not which turned out to be something unrelated. I'm in no way trying to keep this from anybody because I know just how much we all want these damn things. But I would sure love to finish the job that I started but I do not mind handing over what I've got.
---------- Post added at 02:53 AM ---------- Previous post was at 02:40 AM ----------
Josh I just emailed you six pictures I just now seen your email in your post and Justin as soon as I get home if you can shoot me an email or get in contact somehow or I can send you everything I got so far once I get there

Here are the pictures