Seeing as BeagleBoy (http://forum.xda-developers.com/showthread.php?t=1017398) was willing to sacrifice his recovery partition to give us clean boot.img and system.img files, I thought I'd dump my recovery partition from my Xoom Wi-Fi.
*DISCLAIMER* Do not use this to relock your XOOM. I bricked mine... :S
This shows the recovery image from the 3G/4G Xoom is different...
Code:
mac-mini:Xoom Howard$ diff mz600_img/MZ600_HRI39/recovery.img mz604_img/stock/recovery.img
Binary files mz600_img/MZ600_HRI39/recovery.img and mz604_img/stock/recovery.img differ
Code:
mac-mini:Xoom Howard$ cmp mz600_img/MZ600_HRI39/recovery.img mz604_img/stock/recovery.img
mz600_img/MZ600_HRI39/recovery.img mz604_img/stock/recovery.img differ: char 9, line 1
mac-mini:Xoom Howard$
I forgot how to do a binary compare showing how many differences and all that but that's sufficient I think?
Edit: The recovery image I have are from a Canadian Xoom Wi-Fi which is confirmed to be quite different from the US version. US image files for the Xoom can be found here: http://developer.motorola.com/products/software
Here's my recovery partition:
This mean we're able to relock our wifi only Xooms?
Sent from my EvoKneivel
Nope. I think I may have bricked my XOOM in the process.
OP, can you please put a Disclaimer that the files do not work and may brick your xoom. The last thing we need is more people bricking their Xooms and having to return it to the store.
ericdabbs said:
OP, can you please put a Disclaimer that the files do not work and may brick your xoom. The last thing we need is more people bricking their Xooms and having to return it to the store.
Click to expand...
Click to collapse
Done. And to make things worse, I can't find my receipt...
Scourge1024 said:
Done. And to make things worse, I can't find my receipt...
Click to expand...
Click to collapse
Scourge,
Your an absolute renegade, thank you for sacrificing your baby for the benifit of the community. I really hope you find your receipt.
Thanks. I have 3 alternatives...
1. "Borrow" my friend's receipt.
2. Buy another Xoom.
2a. Exchange bricked Xoom with new receipt and sell spare on Kijiji at small loss.
2b. Eat the $600 loss and sell my body to afford another.
I'd only really feel comfortable returning that stuff if there's no serial number, MAC address or other unique identifier on the receipt though.
Will the stock SBF be able to fix it when it comes out?
Scourge1024 said:
This shows the recovery image from the 3G/4G Xoom is different...
Click to expand...
Click to collapse
Just wanted to point out that these would pretty much be different by definition, because they would have different kernels/configuration details due to them being different models.
(It would be interesting to see exactly how they differ, I might go download and unpack them and compare.)
ydaraishy said:
Just wanted to point out that these would pretty much be different by definition, because they would have different kernels/configuration details due to them being different models.
(It would be interesting to see exactly how they differ, I might go download and unpack them and compare.)
Click to expand...
Click to collapse
Well, I thought there could have been a possibility of them being similar. The recovery boot doesn't need to know about all the hardware differences between the two.
Scourge1024 said:
Well, I thought there could have been a possibility of them being similar. The recovery boot doesn't need to know about all the hardware differences between the two.
Click to expand...
Click to collapse
Similar, sure, but there's definitely going to be differences. Remember the boot.img and the recovery.img have the same kernel, ie., the system's kernel, so for efficiency purposes it's not going to have all the CDMA-specific stuff in the Wi-Fi only model.
(If you're curious, I've diffed the ramdisks and can show you the differences, but not the kernel images -- they're compressed and I'm unfamiliar with linux kernel image compression, and I'm not sure what good decompression will do)
Scourge1024 said:
Well, I thought there could have been a possibility of them being similar. The recovery boot doesn't need to know about all the hardware differences between the two.
Click to expand...
Click to collapse
I highly doubt you're bricked bro. Catch me in freenode #xoom and we'll take a look.
I'm just about to grab a power nap. Why don't you think I'm bricked? I can't scroll through the options on the boot screen and in Fastboot and RSD modes, my computer can't see the Xoom at all. How could I have fixed it?
Anyway, I took advantage of an exchange and confirmed that I got the same MD5 for the recovery partition as with the one I extracted from the old Xoom.
heres an easier guide and works only on wifi model http://www.xoomforums.com/forum/mot...99-how-restore-wifi-only-system-boot-img.html
Did you ever get it fixed? As long as you fan get fastboot you're not bricked.
pat4714 said:
heres an easier guide and works only on wifi model http://www.xoomforums.com/forum/mot...99-how-restore-wifi-only-system-boot-img.html
Click to expand...
Click to collapse
has anyone done something like this? i assume this is the closest to a factory reset we can get? I'm not looking to relock, just would like to start over from scratch....
xoppaw said:
has anyone done something like this? i assume this is the closest to a factory reset we can get? I'm not looking to relock, just would like to start over from scratch....
Click to expand...
Click to collapse
Just grab BeagleBoy's boot and system images. I know he extracted them right (virgin copies). The link you provided doesn't site the source or how the images were extracted. But, they could also be his images someone rehosted. I'd go right to the original source though...
http://forum.xda-developers.com/showthread.php?t=1017398
If someone has even once remounted their system folder, it's no longer a virgin copy. Even if they hadn't pushed any files onto it.
Or, you can grab my Canadian Xoom Wi-Fi files here:
http://forum.xda-developers.com/showthread.php?t=1041453
Is there actually a difference between the two? and which would be best for a uk wifi?
Well I had to use the Canadian Image files to recover my uk WiFi Xoom after I got into a boot loop flashing a theme
Sent from my Desire HD using XDA Premium App
Courtesy call. Stock Wi-Fi MZ604 images are up where the MZ600 ones are.
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"?
Hi all,
As the title suggests I would like to flash my UK wifi xoom with the stock US rom to avoid this ridiculous situation of long delays getting what should be routine upgrades from Google, such as a 3.1!
I've read what seems to be most threads on here but wondered if some one could tell me whether it will definately work and point me in the direct of some quick and fairly idiot proof instructions. I'm not looking to root or have non google supported sd card operation, but I would like to receive major firmware upgrades within a week of their US release. So in this instance would just love to have completely stock HC3.1 running.
I'm sure there are loads of uk Xoom users who are in the same situation and would be equally as keen for some definative guidance,
Thanks if you can help!
I think you probably will have to root (or at least unlock your bootloader) in order to remove the software in the first place.
It's pretty easy though, did it myself at the weekend. Used the one click root method in the development section
http://forum.xda-developers.com/showthread.php?t=1011196
Ignore the warnings, but make sure you do choose wifi from within the program. (I'm also on a UK wifi and it worked fine)
From there you can either install 3.1 from this thread
Http://forum.xda-developers.com/showthread.php?t=1074609
Or you can grab the stock system image from the moto website and install that. Personally I think it would be easier to go the first route and keep root, but it's up to you. I can't help with the system image method, never done it before.
I have been tempted by this too, but for my uses at the moment, I wont really gain much, but Ill keep this in mind in case I change my mind
Sent from my MZ604 using XDA Premium App
Also seriously considering this. I'm going on holiday at the weekend though and will need my Xoom in working order so I'll hold off til I'm back. Who knows, we might even have the update by the time I'm back. If not this is definitely my plan.
I'd also really like the UK stock images or to know how to get them off myself just in case.
Sent from my Xoom using XDA Premium App
I don't think there is a uk image yet... although I might have seen a non-us on moto website? Or did I imagine that?
Sent from my MZ604 using XDA Premium App
I have done all of BRD's mods , and its all good chaps
once a uk/euro rom is available I will probs flash that , but for now 3.1 is worth being a yank
nexan21 said:
I have done all of BRD's mods , and its all good chaps
once a uk/euro rom is available I will probs flash that , but for now 3.1 is worth being a yank
Click to expand...
Click to collapse
Can you flash back to stock using a nandroid backup or do the image files go deeper than that?
Sent from my Xoom using XDA Premium App
Wifi models (Ie MZ604) are fine to flash US Boot images (non-3g i might add ) but 3G models are no go and are bricking if trying to install 3.1.
My advice is although it works, i would suggest waiting for the 3.1 UK / Euro updates as there "maybe" compatibility issues (i say maybe because people will go "Oh Wait, there are none")
at the moment i have a working xoom 3G but cant go in the internet using a SIM card... why? why you might ask?
Some strange reason my telephonyprovider.APk has mucked up xd
But anyway, take it easy before you flash, its your problem if you brick.
burden010 said:
Can you flash back to stock using a nandroid backup or do the image files go deeper than that?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
well i cant go back to stock cos the uk/euro version is not available yet , but will be at some point .
so far i have'nt had any issues , touch wood ! (-;
Just updated my UK version to 3.1 by flashing the US wifi image, then re-locked the boot loader. All seems well.
Update too my UK version to 3.1 with the US wifi image, root and install tiamat kernel
then install language package cause I'm French.
All seems well too.
Just a little thing, the web market detects a new device "Xoom Verizon" instead the previous MZ604 device.
elrazerx said:
Update too my UK version to 3.1 with the US wifi image, root and install tiamat kernel
then install language package cause I'm French.
All seems well too.
Just a little thing, the web market detects a new device "Xoom Verizon" instead the previous MZ604 device.
Click to expand...
Click to collapse
yeah , mine is detected as "Xoom Verizon" also
no adverse effects apart from most apps in the market are priced in $'s not £'s , so i'm waiting for uk/euro image to hit !
Mine still says £'s, even when I was accessing the US market via VPN.
Just do it!
The instructions are somewhat hard to find, but...
1. Install the Android-SDK,
2. Make a path to the fastboot command via right clicking Computer selecting properties select advanced system, environment variables, click on PATH and in the variable value input paste:
C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools
3. Make sure you de-zip the stock us Wifi firmware into the C:\Program Files (x86)\Android\android-sdk\platform-tools directory. Download these from the MotoDev web-site.
4. Place your xoom in fastboot by turning off then repowering holding the volume down button to enter fastboot mode.
Open the command prompt if not already open...
Unlock your Xoom by typing:
fastboot oem unlock
at the command prompt.
then enter the following:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Once complete your Xoom should reboot thinking it is a stock US device, so re-configure and you should be prompted with the Update for 3.1.
Job done, no more waiting around like a second class citizen for Motorola to bother passing on the released Google updates to your device. And 3.1 is definately worth the effort...
And yes there is absolutely no reason why European customers paying a premium price point should have to do this to obtain a routine update in a realistic time-frame. Hopefully once flashed to a Stock US device we should receive updates within the same operational window as those who purchased within the US.
Hope this helps, it certainly helped me! (PS this will of course blank your device back to default, once done this should be the last time as updates should now arrive in line with their release!)
pirsiger said:
.... instructions ...
Click to expand...
Click to collapse
Nice - that's the second post of instructions I saw (others are herE: http://forum.xda-developers.com/showthread.php?p=13942581#post13942581)
and as I said then - I think people will still be a little hesitant due to no return to UK image silly Moto
Is there a reason that you would want to go back to a UK image? What is the diff between the UK and US? The only thing I can think of is the UK image Google services connects to servers in UK/Euro.
PsyMonkey said:
Is there a reason that you would want to go back to a UK image? What is the diff between the UK and US? The only thing I can think of is the UK image Google services connects to servers in UK/Euro.
Click to expand...
Click to collapse
If you ever wanted to return it due to a fault (screen, wifi etc) they would take one look at the US software and claim you have invalidated your warranty.
Short it out with 12V DC through inappropriate parts of the internals? Did that with a phone Orange replaced because the replacement was falling apart and the one I sent in was mint externally.
But tbh, I don't think anyone who works in these stores would know much about software versions.
VaKo said:
Just updated my UK version to 3.1 by flashing the US wifi image, then re-locked the boot loader. All seems well.
Click to expand...
Click to collapse
Same here, running sweeeeet
Is there any way to do this without losing data?
Sent from my Xoom using XDA Premium App
I attempted to flash the Motorola Xoom rooted boot.img on my Thrive.
It didn't work.
I have been unable to find a stock(or rooted) version of the Thrive boot.img so I can unbrick my device.
Can someone please
1.Provide a working boot.img
or
2.Instruct me on how to extract it from an intact Thrive?
I guess its safe to assume anyone working on rooting would have a copy of it
I would really appreciate the help!
Edit: I have been looking for hours for information on how to extract the boot.img from a device like this and have been having no luck.
Can someone please help me?
I realize what I did was idiotic...
I'll never mess with anything that says "boot" again unless I really know what I'm doing.
This is why we need a dev forum!
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
In the meantime, I'm getting a call back from level 2 tech Toshiba support in an hour. Trying to convince them to give me a copy of the recent firmware update. So "I can see what they changed, as there was no changelog".
Odds I succeed?
what is the exact model of the thrive?
Toshiba AT105-T1032
P/N PDA01U-00501F
lol while your at it ask for the sbk
joe ferreira said:
lol while your at it ask for the sbk
Click to expand...
Click to collapse
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
joe ferreira said:
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
Click to expand...
Click to collapse
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Well, 2nd level tech support never called me back. Called back tech support and they PROMISED they'd call me back this time, in 2-3 hours.
Here's hoping this lands us an OTA update file
Natolx said:
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Click to expand...
Click to collapse
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Natolx said:
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
Click to expand...
Click to collapse
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
btw root is a part of the system.img not the boot.img
boot.img is the kernel
joe ferreira said:
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
Click to expand...
Click to collapse
yes, that's how I bricked my tablet, by using fastboot to flash a xoom rootboot.img. Fastboot and recovery are available from simple menu by holding down power and volume up when booting up.
The fastboot is completely unlocked from the factory, you don't even have to issue an unlock command.
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
D3MN5PWN said:
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
Click to expand...
Click to collapse
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Natolx said:
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Click to expand...
Click to collapse
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
D3MN5PWN said:
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
Click to expand...
Click to collapse
My recovery is fine, its just the kernel.
My level 2 tech support discussion was a mixed bag. The guy essentially said it was extremely odd that the firmware update wasn't on the website and that they hadn't even heard about it. He sent an e-mail out to his entire department to find out what's going on. Hopefully that gets sent up the pipeline and it shows up under thrive downloads on the support website.
joe ferreira said:
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Looks like none of the oneclick roots work, someone on thriveforums posted this in response to my request.
"Sorry, I tried both the gingerbreak and psneuter versioins, neither worked.
Oh, and I also ran the "Check Drivers" and it said no issue found.
Also found z4root on theunlockr.com and tried it, appears to have hung up my Thrive."
***Updated: 04/09/2015
First, thank you BeansTown106 and ryanbg for previously sharing the information and technical expertise that has led to successful development of the "tool" that ultimately provides the means to recover a locked bootloader on the Note 4 Developer Device. Without your help and expertise this "tool" may never have been developed.
UDATE: 04/09/2015---There is now a step by step guide that will take you through a process that produces a flashable aboot recovery file for the Developer Edition bootloader if it becomes locked (by flashing retail firmware for instance). This backup MUST be done BEFORE your bootloader becomes corrupted and locked. It is strongly recommended that if you own a Developer Edition Note 4 that you take the time to make a backup of your aboot. This link will take you to a step by step process with links to the couple of files you will need.: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911. Thank you radionerd for the guide and again to BeansTown106 and ryanbg.
Most of us have heard or read about Developer Edition owners of the S4 or S5 that inadvertedly flashed a retail firmware or ROM that was not intended (safe) for the Developer Edition consequently turning their Developer Edition phone into a retail edition phone...locked bootloader. I want to emphasize that this method of recovering a Developer Edition bootloader has been tested and has recovered several Note 4 DE devices whose bootloaders were locked (purposely or inadvertently).
I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.
tfly212 said:
I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.
Click to expand...
Click to collapse
Yep, I don't understand either, but it happens.
jpcalhoun said:
Yep, I don't understand either, but it happens.
Click to expand...
Click to collapse
Yeah my Dev edition note 3 got ruined with running "nvbackup" so as a last resort i purposely flashed a retail rom hoping that would just make it work even though it would be locked...
This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.
gatesjunior said:
This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.
Click to expand...
Click to collapse
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Well, that's kind of my whole point I was being a little sarcastic. With a locked bootloader, lets just say Read-Only, you cannot really overwrite something RO that has already been loaded per say... You would have to be able to fastboot, from my experience, in order to be able to do that. Now if they are signing it, if we could somehow impersonate the key and resign with a newer version number that might work, because they probably have allowances for signed updates.
To me, that might be the only way of resolving this whole locked bootloader issue in general. They obviously have the ability to update them, so we need to figure out how to sign it somehow and or understand their conditions. Meaning, what if they are already planning the next planned bootloader version coming within the existing one. So in this case, if it doesn't match what is expected on the check it will fail along with the fact the signature is not correct.
mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Have you tried it from the phone useing Terminal Emulator and the su command?
I could only copy aboot.bak via terminal emulator. I couldn't get through with CMD in windows 7. (I have only copied the file.)
It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.
droidstyle said:
It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.
Click to expand...
Click to collapse
Not all have given up yet ... I am still hard at it.. Ye of little faith..
If anyone wants to send me an image of their aboot for research purposes, it'd make my day
ryanbg said:
If anyone wants to send me an image of their aboot for research purposes, it'd make my day
Click to expand...
Click to collapse
PM sent
wy1d said:
PM sent
Click to expand...
Click to collapse
anyway i can one too/??
larrycjr said:
anyway i can one too/??
Click to expand...
Click to collapse
I'm not certain that p6 is the aboot. I'm thinking it may be p7. I've asked for verification in the other thread.
is there an odin file for the developer edition device? if so will someone direct me there??
larrycjr said:
is there an odin file for the developer edition device? if so will someone direct me there??
Click to expand...
Click to collapse
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.
wy1d said:
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.
Click to expand...
Click to collapse
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.
gatesjunior said:
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.
Click to expand...
Click to collapse
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.
wy1d said:
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.
Click to expand...
Click to collapse
Well....... I would say you covered all the bases... lol
For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.
So the difference in between whats out there and this is? I'm curious as the build is different.
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.
Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app
Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.
Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.
Well no worries this all but confirms vzw is rootable and unlockable
Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx
Is there a rooted version??
Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition
Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.
Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?
How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat
mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA
Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone
Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?