Related
This is the boot.img and system.img from a stock Wifi xoom!
DO NOT USE TO RE-LOCK YOUR ZOOM
How did I get it? I flashed the tiamat boot to my recovery partition, and booted to it. Then I pulled the pristine boot and system partitions.
The system.img is here: http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
IMPORTANT: These are unmodified images from my stock xoom. You can't re-oem-lock with them (probably due to the lack of userdata.img). If you do, you run the chance of a brick. (After seeing a complaint of this, I verified it with my own xoom.)
-Jim
Have you verified that once you are rooted, you can flash back this stock image and relock the wifi xoom?
Is this all we need to flash it back to stock? I looked at the official Stock images from Motodev for the 3g version and their zip file contained 4 files: boot.img, recovery.img, system.img, userdata.img. It looks like you extracted boot.img and system.img. Are the other 2 files (recovery.img and userdata.img) needed?
ericdabbs said:
Have you verified that once you are rooted, you can flash back this stock image and relock the wifi xoom?
Is this all we need to flash it back to stock? I looked at the official Stock images from Motodev for the 3g version and their zip file contained 4 files: boot.img, recovery.img, system.img, userdata.img. It looks like you extracted boot.img and system.img. Are the other 2 files (recovery.img and userdata.img) needed?
Click to expand...
Click to collapse
Recovery shouldn't be change, as there is no aftermarket recovery yet. Userdata will create itself on boot with the new system.
Sent From My Evo
If you should need it for some reason, you can get the recovery image from this thread.
ok guys, i tried this this morning.
pushed the stock images and relocked.
now i'm stuck at FAILED TO BOOT LNX 0X0004.
can't get adb OR the computer to recognize the xoom now.
any ideas??
Chris
Has anyone else tried the stock images posted in this thread?
I've reflashed, and booted with them multiple times with no problem. BUT, they don't appear to be enough to do an oem-lock. If you do, you get the "FAILED TO BOOT" error.
-Jim
Since I was the guinea pig and tried this how do i get it running again?
Windows won't recognize that the xoom is pugged in. ADB just says device not found.
Chris
ke5hde said:
Since I was the guinea pig and tried this how do i get it running again?
Windows won't recognize that the xoom is pugged in. ADB just says device not found.
Chris
Click to expand...
Click to collapse
Chris. Hopefully an expert with this stuff can answer your question soon. If not, do you have the receipt so you can exchange it at the store? I am sure they will take it.
Sure I have the receipt but REALLY don't want to have to return it if I don't have to.
Hoping this can be fixed. I'll just have to wait it out for a while.
You are braver than I, your problem ids one that CAN be fixed..... but not at the moment that I know of.
What happened is, your device tried to OEM Lock but did not have all of the files. So it did in fact flash you back but is missing 2 other core files that were not pulled.
The only way that I know there is to fix this is to actually flash the SBF file through RSD Lite....... there is one problem though. Motorola has not released this yet.
Honestly, your best bet is to take it back and get a new one because who knows when Moto will get off their thumbs and push some simple files online for everyone to use. :-/
Good luck
RSD would be nice but the xoom doesn't even show up there, not really sure if I CAN sbf back since the computer doesn't even know the xoom is connected.
Sent from my liberated Droid X
Well I ran into the same problem with the 3G version and SBF recognized it but nothing else would. Like I said, best bet would be to just take it back and say it is defective and hope they trade it out.... or wait for the complete dump to come out.
stevenege said:
Well I ran into the same problem with the 3G version and SBF recognized it but nothing else would. Like I said, best bet would be to just take it back and say it is defective and hope they trade it out.... or wait for the complete dump to come out.
Click to expand...
Click to collapse
Someone did provide the system dump for the wifi version. Not sure if this will help though.
http://forum.xda-developers.com/showthread.php?t=1011484
No, sorry I meant something else.
I meant Moto needs to release the SBF and the Stock everything so developement can actually get kind of started. The ability to root and un-root is great..... when we can un-root.
The system.img supplied by OP corrected my wifi xoom that I'd bjorked by installing the 3G unlock/root on.
In the interim I'd installed the wifi modules. It ran fine but because it considered itself a 3G it wanted to download and install HR166 update which was getting annoying.
I don't think that these imgs will get you back to OEM/locked but that should be available soon enough from MOTO.
Exchanged....I will no longer be a guinea pig. Lol
Sent from my liberated Droid X
ke5hde said:
Exchanged....I will no longer be a guinea pig. Lol
Sent from my liberated Droid X
Click to expand...
Click to collapse
Thats good
This is the problem with being home with a broken femur and hip for the past 3 months. I do nothing but get in trouble. ;-)
same happened to me quick questions
would you be able to flash 3g abf to xoom and then just reflash everything back to stock once you get it out of the "lock"?
FIRST TRY... Edited system.img (KERNEL 2.6.36.3 only!!!)
WARNING: ONLY USE THIS IF YOU HAVE A BACKUP OF YOUR /DEV/BLOCK/MMCBLK0P3 IF YOU DONT HAVE ONE YET, MAKE ONE BY USING THIS:
IF FROM ADB:
ADB SHELL
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
IF FROM TERMINAL EMULATOR:
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
THIS IS A FUNCTIONAL FILE SYSTEM, I AM WORKING ON A CUSTOM ROM WITHOUT HAVING TO HAVE THE BOOTLOADER UNLOCKED.
THE ONLY THING THAT HAS CHANGED ON THIS SYSTEM.IMG IS THE BOOT ANIMATION (INSTEAD OF "ANDROID" IT HAS THE HONEYCOMB BEE) AND THE FONT HAS CHANGED ALSO...
AGAIN, THIS IS JUST A TEST, IT IS THE FULL FILE SYSTEM TO BE USED ON A DAILY BASIS BUT DOES NOT HAVE ANY OPTIMIZED FILES AT THIS TIME.
Alright, now that you have read the warning... download this file here:
LINK = http://www.megaupload.com/?d=1YZSDVZI = LINK
You can then push the file through ADB by typing:
dd if=/sdcard/blk0p3_sys.img of=/dev/block/mmcblk0p3
Post if it worked for you or if it did not, this will help me troubleshoot...
PLEASE MAKE SURE THAT YOU MAKE A BACKUP OF YOUR FILES FIRST!!! THIS FILE IS BASED ON USA MODEL 1.104.05_GEN1 ACER A500. I RECOMMEND TO TRY ONLY IF YOU HAVE HAD TO UNBRICK YOUR TABLET BEFORE. I DONT WANT TO MESS UP YOUR TABLET!!! YOU HAVE BEEN WARNED!!! JEJEJE
Please post if it has worked for you or if it glitched, I am currently in trial and error so... my tablet gets bricked 1-3 times a day because I am testing different things on the system images... hopefully, I can find a way to have root on the image or at least include:
1. File manager
2. ROOT or at least the Gingerbreak.apk already installed.
3. Terminal emulator
4. Custom background upon boot
As stated, it works for me but I have only 1 tablet so if you are daring enough, please dont hessitate to help me in getting this up and running...
I AM NOT A DEVELOPER SO PLEASE BARE WITH ME AS I AM TRYING TO LEARN AS I GO... JEJEJE
props to you!
u crazy.
I don't see any attachment or link...
Euclid's Brother said:
I don't see any attachment or link...
Click to expand...
Click to collapse
Sorry about that, i've updated the post... jejeje
Beta Rom
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
THANKS!!! this is what I am needing... at this time, there is NOTHING ELSE that has been changed on the file system... I am just testing making sure that my changes stick... I am hoping to be able to change some more things... As long as its working... I will continue changing things ... Until I can get an image that is worthy of "Custom ROM" status... jejeje
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
Did you fix your issue if you haven't I'm on gtalk if you want help I pulled my hair out for 2.5 days before I fixed it
Sent from my A500 using XDA Premium App
cant figure out how to multiquote as clicking the buttons dont do anything.
but just look at "Crsdr37"'s post in general with the imgs and update zip to get back to stock and updates!!!
and to the person who made the IMG keep up the good work. im not gonna flash it and im happy with being stock and getting updates now ;D
Have you figured out how to apply the incremental updates to the img?
I suspect it's just replacing files, I'll look at it when I get to a PC.
Ive been away from my tablet today. I put the post up and went out tonight... jejeje
Thank you guys that tested my image... if it worked for you, THANKS!!! if ou didnt, then let me know what did not work...
THIS IS NOT NOT NOT AN UPDATED IMAGE, IF YOU CHECK THE DESCRIPTION, THIS IS A TEST IMAGE TO GET A CUSTOM ROM OVER TO THE ACER A500... I AM TESTING SO I WILL NOT ANSWER QUESTIONS ABOUT UPDATES... THAT IS FOR MY OTHER POST... SORRY PEOPLE.
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
i am going to try it as well nice thing you guys do
Great
Cheers man, !
So, pulling your system image from /DEV/BLOCK/MMCBLK0P3, then modifying it, then pushing it back works?
Let me try and understand here:
I thought the whole locked bootloader thing checked signatures on the images that are about to be loaded into memory, such as the image in /system.
According to this:
http://www.reddit.com/r/Android/comments/hkbf3/so_you_want_to_know_about_bootloaders_heres_the/
It says:
What does a bootloader do with digital signatures?
It uses them to check any update that passes through it.
So: dd any partition we want to modify, back it up in a safe place, mount the img we get from that, make changes within the img, and dd it back, = all good?
ie: signed bootloaders only have to do with installing update.zips on the sdcard?
Can someone clear this up for me?
Thanks!
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
netham45 said:
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
Click to expand...
Click to collapse
Dude, chill man... You are right, your question does ask about headway for the updates but here are the facts:
You are asking about updates on a BETA Rom that is just in testing...
I took your question to be if the ROM file had the updates (My fault for sure). I was not yelling per say nor trying to be rude but rather making sure that people are aware this is in no way an updated image and should not be treated as such... THIS IS A TEST ROM and since your question was posted within its thread, I took it as if it was directed to the image itself and not toward me and my development...
Look, as stated, im not a developer man, this stuff is a little hard for me to do. I do apologize because I did not answer your question correctly/completely but as far as the comment... Its what I meant. jejeje
tomlogan1 said:
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
Click to expand...
Click to collapse
Have restored to complete US stock. Had a lot of problems related to SD cards, had to swap them out to avoid errors on the actual update.zip file, but am back to normal. Now if I can just keep my hands off until the 3.1 update comes out, or there is custom ROM...
mapaz04 said:
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Click to expand...
Click to collapse
That's what I've doing for a while now....I guess I should have shared xD
been installing custom fonts and trying to change some of the system settings from other customized roms directly from the tablet.
Instead of reflashing wouldn't it be easier to just provide the files to push into the tablet? just my 0.02
Yeah, I can provide files for you guys to install but what I was going for was an image that contained everything already setup so you can just flash it over ur old one allowing the "customization" to appear upon install/pushin the file... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
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
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?
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.