Database Users

Have a Google Edition One? Look here before you do ANYTHING to it!

So it has been reported that GE HTC One's are shipping. We would like to get all the paritions dumped so that we can use the images to fully convert our normal Ones into full fledged Google Edition Ones.
Before you do ANYTHING with it (before you root, before you flash a recovery etc...) Follow these directions courtesy of cschmitt Found Here This will ensure we get all the partitions
I have pasted the steps below. This will help the community out greatly!
cschmitt said:
I have a windows command script that uses adb to dump and pull every partition from a One, excluding cache (meaningless) and userdata (to large).
He would need adb and fastboot on his computer, no need for S-off, since we are only reading partitions.
Generally the process would be:
Enable USB Developer options and USB debugging on phone.
Connect phone to usb, install drivers from zip folder if prompted.
Copy SuperSU-v1.41.zip to sd card.
Reboot into bootloader. (Power off, hold power on an vol-down.)
Open command prompt into \htconedump folder.
Unlock bootloader, fastboot oem unlock should do it.
Reboot back into bootloader (via hboot menu.)
From command prompt:
fastboot erase cache
fastboot boot openrecovery-twrp-2.5.0.0-m7.img (Take note we are not flashing recovery, just booting into it so we can root. If you flash the recovery we will not be able to get the stock GE recovery pulled)
Once TWRP boots, flash SuperSU-v1.41.zip via TWRP to root device.
Reboot back into system.
Run pullmmc01-37.cmd command script from a windows command prompt.
Zip up the dump directory containing all of the mmcblk0p??.bin files.
I've packaged everything up into a zip file containing ADB, fastboot, HTC drivers, superuser.zip, TWRP image, and the pullmmc01-37.cmd command script.
htconedump.zip"
Click to expand...
Click to collapse
Also make sure to take note of your CID in the bootloader and also report that in this thread. You can get this by running fastboot getvar all while in the bootloader. The MID and the CID will be listed. Please make note of both.
I would advise anyone doing it that they do it without fully setting up the phone because once you unlock the bootloader it will wipe your data. So boot into android and just skip through the whole set up process because you'll just have to do it again after you unlock the bootloader
EDIT: Got this info from the Dump thread on Android Central. Just need to confirm it's correct with someone who has the device
ro.product.name=m7_google
cid=GOOGL001
mid=PN0712000
cidlist=GOOGL001

Reserving this space for conversion instructions.

http://forum.xda-developers.com/showthread.php?t=2356654 Using dump of released device??

bobsie41 said:
http://forum.xda-developers.com/showthread.php?t=2356654 Using dump of released device??
Click to expand...
Click to collapse
We have the system and the boot.img but for us to do a full conversation we need the bootloader, the recovery etc.. Sure, we can all run the rom now but if we get ALL the partitions dumped we can essentially convert our normal ones into full fledged google editions (I think if we had just the bootloader and the recovery we would be ok)

Have you asked Mike?

we would need the 4.3 system dump

bobsie41 said:
Have you asked Mike?
Click to expand...
Click to collapse
Mike used the same dump everyone has been using. It was only system and boot not the bootloader or recovery. The guy who did the dump flashed a custom recovery before he did the dump so we did not get the stock GE recovery which is needed if we want a full conversion and be able to get OTA's just like the GE One would get.

hello00 said:
we would need the 4.3 system dump
Click to expand...
Click to collapse
Yeah here is to wishing they ship with 4.3 lol
The idea here is not for us to be able to run the rom but to fully do a conversion. As of now we have the 4.2.2 rom and boot image. I have two ones and I want to fully convert one to a GE. I know others are interested in performing a full conversion as well. And if we do the full conversion when the 4.3 OTA drops we would get it as an OTA and not have to wait for other devs to package it all up for everyone

graffixnyc said:
Mike used the same dump everyone has been using. It was only system and boot not the bootloader or recovery. The guy who did the dump flashed a custom recovery before he did the dump so we did not get the stock GE recovery which is needed if we want a full conversion and be able to get OTA's just like the GE One would get.
Click to expand...
Click to collapse
Ok. I assumed that, due to the delay in Mike releasing his GE rom, that he had perhaps acquired his own information.
If anybody lives in the viscinity of Old York City, struggling to dump the required information, I could offer the same service as you have for those near New York City........Highly unlikely I guess.

I am very interested in trying this out.

RaptorMD said:
I am very interested in trying this out.
Click to expand...
Click to collapse
Hey! I remember you! Didn't you use one of my roms at one time(Either on the HTC View or GS3)? If I remember correctly you're also from NY?

This is a great idea. If not for the missing T-Mobile LTE band I would have bought the GE. I hope you get what you need. Would probably cure my Flashaholics disease too, if you're always up to date with the latest and greatest.
Sent from my One using Tapatalk 2

Yea i cant wait for the dump. I bought this phone specifically to make it a GE. Im on AT&T, running an unlocked Tmobile HTC One. The best of both worlds

graffixnyc said:
Hey! I remember you! Didn't you use one of my roms at one time(Either on the HTC View or GS3)? If I remember correctly you're also from NY?
Click to expand...
Click to collapse
I did on the HTC View and very likely the GS3 as well and I am from NY Its nice to run into you again. The HTC One is finally a phone worth KEEPING, finally. Now that I am off VZW and enjoying GSM and a Developer Edition H1 life is far more interesting.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
serialtoon said:
Yea i cant wait for the dump. I bought this phone specifically to make it a GE. Im on AT&T, running an unlocked Tmobile HTC One. The best of both worlds
Click to expand...
Click to collapse
I look forward to what the devs cook up in the ROM kitchen. I am very keen to try out the GE ROM's but I would also like HTC to just offer up the option for DE to get it now and to allow anyone to flash it if they want.

I am also interested in converting my s4 gt-9505 into a full google edition s4 with OTA.

slikr said:
I am also interested in converting my s4 gt-9505 into a full google edition s4 with OTA.
Click to expand...
Click to collapse
Wrong forum?

surely will try this out

Any news I'm anticipating fully converting to GE!!

Hopefully in the next few hours it will arrive! Cant wait to receive it

Aerys said:
Hopefully in the next few hours it will arrive! Cant wait to receive it
Click to expand...
Click to collapse
Are you going to try to dump the partitions? If so, I would advise anyone doing it that they do it without fully setting up the phone because once you unlock the bootloader it will wipe your data. So boot into android and just skip through the whole set up process because you'll just have to do it again after you unlock the bootloader

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.

[STOCK] VERIZON Nexus 6 [5.1][LMY47E] Firmware Image

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?

Samsung Support is THE WORST!!

Trying to just get my $900 Verizon Note Edge Dev flashed and the third person I am talking to is taking extra time to tweak me, and make me repeat every last bit of information that is in the ticket. It mt 3rd call and the first 2 gave me incorrect info, now this B****!
That girl needs to find a job where she does deal with the public!
Vent over.

Did you get your stock recovery.img yet? If not I found the process in the forum. I haven't had time to try it, hopefully soon.

Nope, still waiting.

I'd have to agree with you... Samsung rep told me i basically wasted $800 on the developer edition as it is no different from retail, locked bootloaders are a default configuration and there is no way to unlock them.
is this true? doubt it, else whats the point of developer editions? I guess we just ned to wait around a bit and see if someone comes up with something.... hopefully soon. towel root didn't work btw lol. gonna try kingroot and 1 click too. i'm scared to try and of the CF auto methods they are all for other carriers and i dont want to end up soft bricked...
if i am able to get something from this i'll let you all know.

They don't even know their own products...call 3 times, get 3 different answers (literally happened to me). Love Samsung products, but will never rely on their support.
NekoShinigami said:
I'd have to agree with you... Samsung rep told me i basically wasted $800 on the developer edition as it is no different from retail, locked bootloaders are a default configuration and there is no way to unlock them.
is this true? doubt it, else whats the point of developer editions? I guess we just ned to wait around a bit and see if someone comes up with something.... hopefully soon. towel root didn't work btw lol. gonna try kingroot and 1 click too. i'm scared to try and of the CF auto methods they are all for other carriers and i dont want to end up soft bricked...
if i am able to get something from this i'll let you all know.
Click to expand...
Click to collapse

docugod said:
They don't even know their own products...call 3 times, get 3 different answers (literally happened to me). Love Samsung products, but will never rely on their support.
Click to expand...
Click to collapse
It all depends on the support center/staff you visit or speak to. Have had good experiences on this end of the globe.

NekoShinigami said:
I'd have to agree with you... Samsung rep told me i basically wasted $800 on the developer edition as it is no different from retail, locked bootloaders are a default configuration and there is no way to unlock them.
is this true? doubt it, else whats the point of developer editions? I guess we just ned to wait around a bit and see if someone comes up with something.... hopefully soon. towel root didn't work btw lol. gonna try kingroot and 1 click too. i'm scared to try and of the CF auto methods they are all for other carriers and i dont want to end up soft bricked...
if i am able to get something from this i'll let you all know.
Click to expand...
Click to collapse
I'd say the vzw note 4 cf auto root may work but I would ask chainfire before doing it also person you talked to is stupid If you bout the DE from Samsung it has an unlocked bootloader which allows for root and other various thing like twrp or cwm recovery
Sent From The EDGE

Ah I'm past that lol. Just skipped root straight flashed twrp in Odin then used twrp to flash supersu update zip and was good to go. Now I have a whole new problem though lol. I noobed out and forgot to do a backup before deleting stuff and I deleted something I shouldn't have. Now I can't make or receive calls. Internet works fine, but when I try calling or texting I get "mobile network unavailable."
I tried to get samsung to send me stock recovery for it and they couldn't. Tried asking others here who had the phone also but no luck there either. Probably just gonna have to buy another one...
Sent from my SCH-I545 using XDA Free mobile app

I posted the stock recovery...
http://forum.xda-developers.com/showpost.php?p=59874945&postcount=892
Hope it helps...
NekoShinigami said:
Ah I'm past that lol. Just skipped root straight flashed twrp in Odin then used twrp to flash supersu update zip and was good to go. Now I have a whole new problem though lol. I noobed out and forgot to do a backup before deleting stuff and I deleted something I shouldn't have. Now I can't make or receive calls. Internet works fine, but when I try calling or texting I get "mobile network unavailable."
I tried to get samsung to send me stock recovery for it and they couldn't. Tried asking others here who had the phone also but no luck there either. Probably just gonna have to buy another one...
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse

docugod said:
I posted the stock recovery...
http://forum.xda-developers.com/showpost.php?p=59874945&postcount=892
Hope it helps...
Click to expand...
Click to collapse
I tried to flash that and got stuck on boot lol. I'm not sure how to change it to a .tar or into an actual flashable recovery. I tried to use 7zip to extract that then compress it into a tar but I still couldn't flash it. How was it you were able to get the recovery? The guide I read involved taking the update via kies then copy and paste the image from your temp folder.
Sent from my SCH-I545 using XDA Free mobile app

Maybe with the tool here http://forum.xda-developers.com/showthread.php?t=2281287
You can do just step 5 (since you already have the recovery.img), then use Odin to flash?
NekoShinigami said:
I tried to flash that and got stuck on boot lol. I'm not sure how to change it to a .tar or into an actual flashable recovery. I tried to use 7zip to extract that then compress it into a tar but I still couldn't flash it. How was it you were able to get the recovery? The guide I read involved taking the update via kies then copy and paste the image from your temp folder.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse

docugod said:
Maybe with the tool here http://forum.xda-developers.com/showthread.php?t=2281287
You can do just step 5 (since you already have the recovery.img), then use Odin to flash?
Click to expand...
Click to collapse
I tried, but that program fails. when i run normally it says
bin/tar: value 4294967295 out of gid_t range 0..2097151
bin/tar: exiting with failure status due to previous errors
(then it asks me 6 times to thank him on XDA lol)
when i run as admin i get a similar response but it says
the system cannot find the patch specified.
the system cannot find the patch specified.
the system cannot find the patch specified.
(3 times just like that, then asks for thanks 6 more times)
i tried to redownload the recovery just in case i got a bad download but still same outcome.
When you extracted that recovery file did you also get the stock rom? if so could you by chance post that? or a twrp backup of stock?

NekoShinigami said:
I tried, but that program fails. when i run normally it says
bin/tar: value 4294967295 out of gid_t range 0..2097151
bin/tar: exiting with failure status due to previous errors
(then it asks me 6 times to thank him on XDA lol)
when i run as admin i get a similar response but it says
the system cannot find the patch specified.
the system cannot find the patch specified.
the system cannot find the patch specified.
(3 times just like that, then asks for thanks 6 more times)
i tried to redownload the recovery just in case i got a bad download but still same outcome.
When you extracted that recovery file did you also get the stock rom? if so could you by chance post that? or a twrp backup of stock?
Click to expand...
Click to collapse
I think u need to download stock firmware from Sammobile and flash it via Odin first.

They don't have the Verizon stock firmware
Sent from my SCH-I545 using XDA Free mobile app

Make ENG boot(adb enable file)

Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950

jumam21 said:
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
Click to expand...
Click to collapse
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk

Re
rudimenta said:
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
I mean How can I make ADB enable file from combination File.

jumam21 said:
I mean How can I make ADB enable file from combination File.
Click to expand...
Click to collapse
Exynos? I hope so because there is no sboot file for snapdragon ?
You don't need the factory boot for exynos. Just enable OEM unlocking

partcyborg said:
Exynos? I hope so because there is no sboot file for snapdragon
You don't need the factory boot for exynos. Just enable OEM unlocking
Click to expand...
Click to collapse
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.

noidodroid said:
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
Click to expand...
Click to collapse
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google

partcyborg said:
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
Click to expand...
Click to collapse
This has also been told to me by a mod ive spoke with time to time but the others really don't seem to mind as long as it is to help others and such. Which is what i do when i put up a manual tutorial. I usually do all by freestyling (no looking into anything unless really needed). If the same PartyCyborg from Android Forum Community. We don't know each other but I have used your work past and present and had a swell time finding through archives but this i enjoy. Very cool work man esp the last bit i asked you about on i believe an older Samsung 2014? device to action with your Rom's latest. Alright back to AndroidForum Community I have explained my whole outlook & debated the whole FRP issue with phones today. It's a challenge and it's helpful to those that aren't running masses of stolen phones through boxes (hey even stolen hardware once seized returns back to the community and has to be delt with.. i as do others get some devices from LEA property) and also that huge majority of people who quickly create accounts without jotting down and remembering info. Then i could go back into bulk onto stores who legally obtain (auction for example) then have to either a) find a way to fix frp and or 2) resell these devices 3) part out as google locked LB's etc. Google Lock and FRP in general is a VERY good thing IMHO. I want to see us make a move to more secure reliable FRP locks such as iClouds. We also have a security section here on XDA where all sorts of the latter and even deeper is discussed. Win Win for Security overall if you think about it all and take it in. I've said this before in other Areas of the internet I am from and I will say it again in similar words "they build it, we bypass it, they improve it.......(reversing.. updating.. learning.. phase) and the process continues.". We are improving security on everything be it my old days email filters (especially the old ways) or be it Google Lock Security & FRP and the countless other companies small and big across the globe with related protection put in place. Don't put a dark hat on it all.. at least just yet. -not directed toward you by any means or anyone else.. just my quickie worth of that whole 2 cents for what its worth.