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

New Brazilian firmware

Hi guys!
Just saw at SBf Developers that hey have uploaded some new updates there.
AS my comes from Brazil, i saw that fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz is avaliable. But my question is: how can i flash this kinda if files since they arent RSD lite type and are fastboot ones? Do i need unlocked bootloader?
If someone can help me, i appreciate a lot!

AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file

waiflih said:
AFAIK, RSD is only a front end for fastboot, so technically you can flash those files with fastboot, because they are stock and signed by motorola (no unlocked BL needed). You just have to know the partitions in wich you're gonna flash each file
Click to expand...
Click to collapse
Thanks my friend! But do uo have the steps for this? Cause i couldnt found any specific to Moto X.
As i unzip the tar file, i have these files as attached.

I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards

waiflih said:
I don't have the exact steps, but you can look at the flashall.bat file inside your zip
regards
Click to expand...
Click to collapse
Thanks again!
Any ideas?

Do you have the phone in fastboot mode and connected to your PC while running the BAT file?

xitake said:
Do you have the phone in fastboot mode and connected to your PC while running the BAT file?
Click to expand...
Click to collapse
No,but as the programa asks, i don have a JTAG flex?

xpc21 said:
No,but as the programa asks, i don have a JTAG flex?
Click to expand...
Click to collapse
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go

xitake said:
I also didn't know what a JTAG flex is. After some googling, it seems that it is a sort of cable for flashing the image directly to the memory, internally, like in the photo below (not a Moto X).
So, I assume you don't have a JTAG flex connected, right? So it should be good to go
Click to expand...
Click to collapse
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.

Flahing stock SBF
xpc21 said:
Have you my friend flash or know about fastboot program? Case i have in more popular android phones but Moto X is so new that i dont wanna risk doing something wrong.
Click to expand...
Click to collapse
Try this maybe it'll work
1. Connect your Moto x, make sure developer options is enabled and tick usb debugging.
2. open command window on the folder including the new extracted firmware.
3. Type adb devices to confirm that Moto X is detected by your computer.
4. Type adb reboot bootloader, Moto X will reboot in fastboot mode.
5. Run the batch file flasfall.
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.

kkhadr said:
Try this maybe it'll work
...
wait until it finishes it might take sometime, and you'll see the flashing process on both computer and Moto X.
Click to expand...
Click to collapse
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?

Anyone else?
[email protected]

xitake said:
Is it OK to do this if the phone is rooted and modified with xposed modules?
Also, from what I can see, this is the version .35
So as it is older than .51, pwnmymoto should still work, right?
Click to expand...
Click to collapse
If this version includes the camera patch then it won't be rooted, but I flashed TMO 4.3 the test build it's working great but off course I lost root, and I'm sure in a few days it will be rooted again, so nothing to fear.

this is the OPs 3rd post about the same topic. One under q&a, one under dev that got moved to q&a, and now one under moto x general. Someone needs to teach him a lesson because he has gotten responses on all three threads. Really frustrating. Won't be getting anymore help from me...

Looks like fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brasil-BR.tar.gz have the same camera app as in ATT, TMO, Sprint after OTA (with improved camera). Camera app in new Brazilian firmware have version 3.0.211 - the same as in TMO rom with OTA installed.

Kind of straight forward
You just need to unpack the tgz container. Inside the folder there is a bunch of files.
I'm my case since I'm using OSX I just ran flashall.sh and done. There is a flashall.bat that I believe is designed to work with windows.
Put your phone in bootloader mode, connect the cable, go to folder the files lies and run the command. In about 5 minutes it is done. :good:

Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?

rodrigorox said:
Have anyone tried it? I was trying to wait for the official OTA update, but it's taking too long. I need to know if it's safe.
Oh, and what if I use other flashboot file like from Verizon instead of the brazilian retail one? Is there any problem?
Click to expand...
Click to collapse
rodrigorox,
I have called motorola on friday and it seems we will be getting the update in the next week or so...
I'd hold on on flashing it if all you look for is the OTA that US got.

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

Bootloader unlocked warning (on boot)

Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks

ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.

just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
It really doesn't matter. I just would like a cleaner boot cycle. Plus I know the MXPE is able to remove this warning.

There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.

fury683 said:
There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.
Click to expand...
Click to collapse
what do you mean? My warning is in orange.

collinjm01 said:
what do you mean? My warning is in orange.
Click to expand...
Click to collapse
http://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/

ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
.
After reading info on Android Security in this link you should know more about Verified Boot.
.
http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
.
.
Techie info about SafetyNet anti-tamper detection here.
https://koz.io/inside-safetynet/
.
Interesting reading about what info Google is now able to pull from youe device.

It's an eyesore no doubt about it but I hardly reboot so it's somewhat bearable.

^^^ why did you bump a thread that died November 11 :lol:

Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.

sn0warmy said:
Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.
Click to expand...
Click to collapse
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.

j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Click to expand...
Click to collapse
Thanks for this update! Will look forward to seeing you post back...while it's not life or death to me it is a rather silly and pointless message by the 100th time I've seen it lol so I would disable it in a heartbeat if I could

just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
No? How about Ya there should be maybe the cause they have a remove mod for the 5x over in the 5x XDA side.
Maybe the same process cause I wondered this question myself
Sent from my Nexus 6P using XDA Free mobile app

j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.
Click to expand...
Click to collapse
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.

You need a custom bootloader to remove this. No kernel will take care of it for you. The warning message is within the bootloader.img. The 5x and the 6p are completely different phones. Regardless of the fact that they are both Nexus devices. What works for one will not necessarily work for the other.
Sent from my XT1080 using Tapatalk

Yeah, I've been quickly discovering that over the past 2 days. Very different phones indeed.

bouchigo said:
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.
Click to expand...
Click to collapse
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app

androidddaaron said:
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I tried it earlier in the morning, and no go. I believe the /imgdata partition does not exist in the N6P, that's most likely why it was commented out from fstab.
Sent from my Nexus 6P using Tapatalk

SyCreed said:
hey guys i don't want to open a new topic cuz i think it's related here -
If i go back to fully stock, and re-lock the bootloader + factory reset after those operation, no one actually can know if the device was rooted or unlocked right?
Click to expand...
Click to collapse
Correct, if you do that it will be like out of the box.

Anyone with a TWRP flashable stock rom for MetroPCS xt1765 Perry Qualcomm

Unfortunately all the TWRP flashable roms from GetOffMyLawn&!+¢#{$ are dead and I need the stock rom for the MetroPCS variant. Anyone know where I can find it?

I think I mostly got to where I needed to go with the stock factory roms without using TWRP. After attempting and failing to make a flashable rip with Android Kitchen, I read about and saw a video on RSD Lite here youtube.com/watch?v=njXQYn53SPc (sorry can't hyperlink since my post count) It basically just quickly shows what it should look like and how it should work IF it works once setup. But it was good enough. The images I had were giving me failing to flash gpt and bootloader errors. So I manually took those complete lines out of both the flashfile.xml and the Servicefile.xml. After that it flashed everything and rebooted. To my surprise I'm not bricked and back on stock. I had to go back to enable Device Carrier Unlocking through the metropcs app (oops). Now I have to probly unlock the bootloader and root again but this time I'll make that backup
But if anyone has the flashable zips, a new upload would be nice for others.

unrooty said:
I think I mostly got to where I needed to go with the stock factory roms without using TWRP. After attempting and failing to make a flashable rip with Android Kitchen, I read about and saw a video on RSD Lite here youtube.com/watch?v=njXQYn53SPc (sorry can't hyperlink since my post count) It basically just quickly shows what it should look like and how it should work IF it works once setup. But it was good enough. The images I had were giving me failing to flash gpt and bootloader errors. So I manually took those complete lines out of both the flashfile.xml and the Servicefile.xml. After that it flashed everything and rebooted. To my surprise I'm not bricked and back on stock. I had to go back to enable Device Carrier Unlocking through the metropcs app (oops). Now I have to probly unlock the bootloader and root again but this time I'll make that backup
But if anyone has the flashable zips, a new upload would be nice for others.
Click to expand...
Click to collapse
Send me an untouched stock system.img, boot.img, and oem.img and I'll compile you a TWRP flashable ROM. If you're not sure how to dump partition images, the best way is to download an app called Partition Backup & Restore. It's a free app and was created by an XDA dev @wanam.

Hey, thanks for the offer. I'll do it. I have the img files that you need ripped and rared. Just been having some connection issues today while attempting to upload the file. I don't know how I should upload it so I'm going to use my google drive and share the link with you either here or by PM if I can't link it here due to the spam protection. Hopefully I'll have it to you within the next day if my connection becomes stable enough to upload.

https://drive.google.com/open?id=1x65mPUAWWm1heQsDRpgm6QYnyyOIp8P5
Here you are MotoJunkie01, I decided to keep the extended name on the file to show exactly what Partition Backup and Restore spit out should there be something different that's needed.

unrooty said:
https://drive.google.com/open?id=1x65mPUAWWm1heQsDRpgm6QYnyyOIp8P5
Here you are MotoJunkie01, I decided to keep the extended name on the file to show exactly what Partition Backup and Restore spit out should there be something different that's needed.
Click to expand...
Click to collapse
I made one yesterday. Read my guide carefully. Have fun. https://forum.xda-developers.com/mo...-stock-rom-t3777830/post76234878#post76234878

Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.

unrooty said:
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
Click to expand...
Click to collapse
Good choice. I, personally, don't see how that's a better option than just rsdlite. But to each his, or her, own. If you need no verity, magisk, and all the basics anyway, why not just flash the stock firmware. No risk involved.

unrooty said:
Quite the write up there, thank you for it it's very informative. But to be fair flashing through RSDLite it working for me so I suppose I'll stick with it. It seems more straightforward afaik.
Click to expand...
Click to collapse
Yep - seems a better choice. RSD Lite isn't the friendliness beast but it's not a bad ride once you understand the idiosyncrasies.