Related
***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
For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.
So the difference in between whats out there and this is? I'm curious as the build is different.
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.
Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app
Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.
Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.
Well no worries this all but confirms vzw is rootable and unlockable
Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx
Is there a rooted version??
Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition
Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.
Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?
How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat
mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA
Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone
Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?
Ok guys, new here and I've done a bit of reading on this already. From what I gather, the S7 Edge is difficult if not impossible to unlock without a factory reset. Here's the issue.
This phone belongs to my friend's husband who was severely injured in an accident at work. He's in a coma and probably won't survive. He was severely burned over 90% of his body with chemicals and he has no fingerprints to unlock the fingerprint scanner. In addition, his wife doesn't know his password, so I figured I'd see if I could do anything for her. I tried the Dr. Fone program, but it's apparently incompatible with the S7 Edge. He keeps getting texts and messages and we can't check them. The phone is also set for a daily alarm at 1:30 AM, and apparently you can't power it down without the lock code either. Ideally, I'd like to either gain access for her or at least extract what data we can from the thing before factory resetting it. It would also be nice to power it down so that it doesn't keep putting out an alarm every night in the middle of the night. All his contacts with his family are inconveniently stored in the phone as well. It's kind of a worst case scenario.
Any assistance or recommendations for a course of action for this situation would be fantastic. I don't have any other information on the device itself other than that it's running on Freedom Mobile's network in Ontario, Canada. They've said they can factory reset it for her, but we were trying to avoid that and get any contacts or messages from his phone if possible.
Thanks in advance for any help! I know it's a long shot!
Edit: I managed to power down the phone with the Power Button/Volume Down trick after about 9 tries, so at least the alarm won't go off. Other than that, no luck.
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
UnNaMeD__ said:
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Click to expand...
Click to collapse
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Use odin 3.13 the latest
Then download twrp recovery 3.2.2.0 tar file for hero2lte the latest.
Boot your phone into odin mode by restarting your phone while holding power home button and vol down. When your reach the confirmation screen press OK.
Open odin and put the tar file in the ap slot and click the ap box and hit start to begin flashing.
Now restart ur phone by holding power home and vol down then immediately hold power home vol up to reach custom recovery.
Edit I just tested this myself
Flash the zip file from this thread no need to go looking for files in system.
https://forum.xda-developers.com/showthread.php?t=2780696
Should remove password pin or pattern.
To check if it's network locked just look at the back of your phone if it says 935u or Verizon wireless or 935W8 then the phone is unlocked for different networks.
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
UnNaMeD__ said:
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
Click to expand...
Click to collapse
maxlords said:
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
Click to expand...
Click to collapse
Hey alright no problem.
Download TWRP for G935W8 from official TWRP website:
https://teamw.in/samsung/samsunggalaxys7edge.html
You can follow some instructions from this thread regarding flashing:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Flashing TWRP might cause your phone to not boot. You will need to download dm-verity disabler from the thread above.
So download TWRP, Aroma file manager, dm-verity bypass, and zip file to disable pass that the other user posted: https://forum.xda-developers.com/showthread.php?t=2780696
Download all these files and put aroma file manager, dm-verity bypass and that password zip file bypass on your SD.
Make sure auto reboot is disabled in odin, follow instruction in thread about how to install twrp. If the auto reboot is disabled, phone will just remain at the same screen, so after the flashing is done from odin. You need to force reboot on your phone (volume down + power button for few seconds), just when the screen goes off, you need to immediately press recovery button combination (vol up + home + power). Here once you enter TWRP recovery see if you can enable MTP and trasnfer data to PC, if not, goto install zip and try password bypass zip file. If it works file then ok and proceed to install dm-verity bypass file and reboot your phone. If that zip doesn't works. You need to go to same install zip file option and now install aroma file manager. From there delete the password files that I told you about earlier, flash dm-verity and reboot again.
Thats it, if get confused about a step, tell me.
Well, I attempted to install TWRP through the latest version of Odin, but it didn't work. The error message I got in Recovery/Download mode was:
"Custom Binary (RECOVERY) Blocked By FRP Lock."
I looked that up online and apparently to install TWRP, I need to remove the FRP lock. I found a program called RealTerm which can supposedly bypass the FRP lock, but it doesn't seem to be connecting to the locked phone and it's not exactly user friendly.
Am I missing something here? Or is there no way to bypass the FRP lock on the unit?
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
Hello, thank you very much for reading, I hope you can help me. I need one or more files to be able to recover my phone: Samsung Galaxy S7 Active.
These are the files that I need:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
I do not know if I would also need these:
MPRG8996.hex
rawprogram_unsparse.xml
I think these files are the same as prog_emmc_firehose_8996.mbn (.elf):
8996_msimage.mbn
MSM8996.mbn
How did I make a brick my phone? Installing the first official version:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
Previously I used this version without any problem:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
I wish someone could help me, I have read more than 50 pages, but I have not been able to solve the problem.
Please.
Can anybody help me?
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
I hope someone helps us.
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
yakine13 said:
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
Click to expand...
Click to collapse
Hello, sorry for my bad English. My phone is a Samsung Galaxy S7 Active (SM-G891A). I will try to explain what happened.
I had this version of Android 6 installed (via Odin) on the phone:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
With that version my phone was fine, but then I tried to install the first version of Android 6 (official) via Odin:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
When the installation was completed (Odin said the installation was successful), the phone never restarted. There is no way to turn it on with any combination of buttons, nor with a microSD with a debrick.img. A USB JIG has not worked for me either.
Windows detects my phone in Qualcomm 9008 mode. Odin does not detect it.
did you find a solution?
actually it look like to be a hard brick but as it's snapdragon 820 you can recover from it
I'm waiting for the day when noobs and half-noobs (no offense, all of us have been there) will start reading before writing and stop assuming that their 1st aid kit will revive a kitten ran over by a train.
It's okay not to know, but before writing a spam reply, just consider for a second that the user already tried your solution and is already a step ahead.
Listen guy, go to Halab Tech. They have certain firmwares for what you need, but they ask money.
Those type of firmwares have a prefix "DEBUG_EMERGENCY_DOWNLOAD_FA....'
In my case it's "DEBUG_EMERGENCY_DOWNLOAD_FA70_G955U1SQU6ASG1_CL12542406_QB24669289_REV00_user_mid_noship_MULTI_CERT.tgz"
As I consider that a bastard move (since they are selling Samsung's intellectual property as their own, stuff that should be public in the first place), I encourage you to share the files if you buy them, so that we can all use them and screw over these monopoly playing-intellectual property stealing bastards.
I'm now working on a recovery of my G955U1 (S8+ Qualcomm USA). I paid $25 for a god damn firmware and I'm gonna post it in next couple of days.
I'm personally having trouble of flashing the firmware (because not many flash tools support flashing .elf flash loaders), but I used one FRP tool (Octoplus FRP tool) to check the loader and it managed to send it, receive the "hello" packet, read partitions and erase the FRP partition (I assume it worked by the log), but I don't have a way to flash other partitions yet.
You people should have in mind one thing: even though certain devices have the same chipset, doesn't mean that you can use the same firehose flash loader, since manufacturers create different loaders for them and write their digital signatures into the chip (don't know is it hardwired or flashed), meaning that you cannot use Xiaomi's prog_ufs_firehose_8998_ddr.elf (just an example) to flash a Samsung device with MSM8992 chipset.
In fact, I think that each phone model and possibly even it's different firmware revisions have unique loaders, since I didn't manage to get a successful response from my G955U1 by sending G955U2 loader, and the loader which I managed to send is actually stated to be for G955U1U6 (U6 is the bootloader revision number, while U1 is the part of the model number).
Best of luck, contact me if you need help.