Here are the .IMG files that Motorola has posted on their MOTODEV site. .
ATTENTION: DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
These files are from Motorola's Development site but I take no liability with anything that happens with your device if something goes wrong.
Official HRI39 Motorola .IMG files:
http://www.multiupload.com/9XP1B8LSWC
Official HRI66 Motorola .IMG files:
http://www.multiupload.com/POUDJY1255
The following are the steps from the MOTODEV site
1. Extract files into android sdk /tools folder.
2. Start command prompt/ terminal from the android sdk tools folder. (How this is done on Mac I do not know, Windows: shift+left click and select "open command window here")
3. adb reboot bootloader
4. fastboot flash boot boot.img
5. fastboot flash system system.img
6. fastboot flash recovery recovery.img
7. fastboot flash userdata userdata.img
8. fastboot erase cache
9. fastboot oem lock
The device will lock and reboot.
You are now back to out of box state. However I do not know if it is still detectable by VZ Moto if you have unlocked the device after doing this.
Also fyi the sbf file is still an option but you will have to go in and do the fastboot oem lock after it completes
u mispelled cache
Fixed. Thanks had a long day and missed that at proof reading
Thanks for the files, does seem a lot simpler to just use the sbf file though.
bwcorvus said:
Thanks for the files, does seem a lot simpler to just use the sbf file though.
Click to expand...
Click to collapse
Its always good to have more options and the Xoom gives us many and hopefully soon sdcard support will provide the final key piece, the CM recovery!
In the meantime it is very good to have all of the official files at our disposal.
If anyone is wondering what the the reflash file from the first leak is, it is an SBF format installation of the stock boot image and a blank user data image to wipe data and return to stock via RSD Lite without touching the system partition.
This provides yet another way to reset that should be examined, especially if it works over a modified system partition.
We also may be able to use any or all of these files to build our own SBF files and other one step solutions for recovering and or modifying the Xoom. This can be very valuable and must also be thoroughly explored along with the NVM so we can really start to tak better control of the radio functions.
Lots to look at...
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
jmc2543 said:
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
Click to expand...
Click to collapse
Yea having these images is one BIG step...now we just need sdcards
Just finished doing this. I'm back at stock. Of course no I'll b the last to get an update. And by the same time tomorrow I'll be unlocking and re-rooting.
by doing this does it erase everything on your xoom?
bishop72 said:
by doing this does it erase everything on your xoom?
Click to expand...
Click to collapse
Yes it would. Itll bring it back to what it was like when you first bought it.
For those that updated, were you able to reroot?
17akota said:
Yes it would. Itll bring it back to what it was like when you first bought it.
Click to expand...
Click to collapse
I saw multiple threads about Titanium backup not working with the Xoom. Are there alternative apps that will save all my configuration like home screen layout etc? It was a lot of work B-)
Sent from my Xoom using Tapatalk
It is just Android 3.0
3.0.1 is HRI66
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Aaron636r said:
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Click to expand...
Click to collapse
Oh no. I did the "fastboot oem lock" and now I get "Failed image LNX 0x0002". Cant boot past Dual Core logo screen.
Ok, re-unlocking it fixed it.
Ok so we have the original flash so we can get the OTA thats great. And Moto confirmed on their forum they will upgrade devices that have been unlocked and rooted. If they cannot install the software they will ship it back with just the new hardware. Can't wait to see what people can really start doing now.
For those of you that are like me and hate having to using mega upload and crap to download things here is a direct link on my web server to the file released by Moto.
DMCA Noticed by Moto
This was taken directly from the Moto Dev site myself.
If you browse the directory, which I think I left on for this one... There is also the sbf archive and RSD there to download. If anyone needs a place to store some files let me know. I have unlimited storage and bandwidth. When some of the OG Droid releases came out I was pumping over 11GB a week in downloads with no issues. It's the least I can do to help the community.
I got to be honest I don't know what the hell i should do to get the update and what will cause me to either have a clean install or lose root
All reports so far indicate it will not break root and rooted users have been getting the notification. They are also probably doing a controlled rollout if you have not yet gotten the notification. My XOOM is at home right now which sucks I won't be able to get my hands on it for about 6 hours and see what I can all do.
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"?
Hello all uk wifi xoomers
Have you noticed the motoblur applications when you go to manage applications> all?
Have you noticed your still on 3.0.1
Well flash the us image files.
I bit the bullet and did it.
got the 3.1 update and is so much faster and the browser works so much better/faster
The whole os seems to be faster as well
Also no more motoblur crap.
Also means when the next update comes out you will get it rather then waiting
I recommend it to any uk xoomer.
Only works on wifi do not try on 3g
Sent from my Xoom
Have to agree, wasn't sure what I was doing when I tried it, but just unlocking the bootloader, flashing the US files and re-locking the bootloader took all of 20 mins, and the device seems to fly now.
iammodo said:
Hello all uk xoomers
Have you noticed the motoblur applications when you go to manage applications> all?
Have you noticed your still on 3.0.1
Well flash the us image files.
I bit the bullet and did it.
got the 3.1 update and is so much faster and the browser works so much better/faster
The whole os seems to be faster as well
Also no more motoblur crap.
Also means when the next update comes out you will get it rather then waiting
I recommend it to any uk xoomer.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
If you do this on a UMTS 3G Xoom you will most likely lose 3G (or have boot issues) and not be able to revert successfully to stock because Moto hasn't released those images yet.
There are already threads about people complaining about this.
Changed post due to only being able to do this on wifi Xoom
Sent from my phone
VaKo said:
Have to agree, wasn't sure what I was doing when I tried it, but just unlocking the bootloader, flashing the US files and re-locking the bootloader took all of 20 mins, and the device seems to fly now.
Click to expand...
Click to collapse
After unlocking the bootloader, do you need to root in order to flash the US files?
Which thread did you use to go by cause i'm not 100% about doing this to my xoom. I have rooted my nexus one though a while ago and am quite rusty to all of this again. ADB is such a nervous step for me!
I used this guide
http://forum.xda-developers.com/showthread.php?t=1052644
I did it from stock.
didn't have root or anything like that
Very easy quick process.
Sent from my Xoom using XDA Premium App
seakins said:
After unlocking the bootloader, do you need to root in order to flash the US files?
Which thread did you use to go by cause i'm not 100% about doing this to my xoom. I have rooted my nexus one though a while ago and am quite rusty to all of this again. ADB is such a nervous step for me!
Click to expand...
Click to collapse
Here is what I did, started with a stock unrooted device:
adb reboot bootloader (brings up fastboot)
fastboot oem unlock (follow on-screen instructions, will reboot, skip everything and enable debug mode again)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w (needed to clear the userdata, otherwise it might softbrick or something due to differences between the US and UK software)
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All done, although afaik you can't go back to the UK software after doing this, and if you try this on a UK 3G Xoom you will be the proud owner of a £600 paperweight.
Basic guide to setting up adb and unlocking the bootloader here, and the images are here. Read every page of the thread iammodo linked to, and understand that as soon as you enter the first flash command for boot.img, you cannot stop until you have finished the entire process.
VaKo said:
Here is what I did, started with a stock unrooted device:
adb reboot bootloader (brings up fastboot)
fastboot oem unlock (follow on-screen instructions, will reboot, skip everything and enable debug mode again)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w (needed to clear the userdata, otherwise it might softbrick or something due to differences between the US and UK software)
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All done, although afaik you can't go back to the UK software after doing this, and if you try this on a UK 3G Xoom you will be the proud owner of a £600 paperweight.
Basic guide to setting up adb and unlocking the bootloader here, and the images are here. Read every page of the thread iammodo linked to, and understand that as soon as you enter the first flash command for boot.img, you cannot stop until you have finished the entire process.
Click to expand...
Click to collapse
Nice - all we need now is a video guide
I think some people will still be hesitant due to no return to UK image - a shame really that Moto haven't pushed it out there.
VaKo said:
Here is what I did, started with a stock unrooted device:
adb reboot bootloader (brings up fastboot)
fastboot oem unlock (follow on-screen instructions, will reboot, skip everything and enable debug mode again)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w (needed to clear the userdata, otherwise it might softbrick or something due to differences between the US and UK software)
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All done, although afaik you can't go back to the UK software after doing this, and if you try this on a UK 3G Xoom you will be the proud owner of a £600 paperweight.
Click to expand...
Click to collapse
Thanks for the how-to-do guide, really spelt it out!
I totally appreciate the importance of reading the pages and pages of info. Spent a full 2 weeks reading before i rooted my nexus one. Shame, i think my nexus is feeling left out! Might flash something on that again before the xoom to remind me of what i'm doing!
seakins said:
Thanks for the how-to-do guide, really spelt it out!
I totally appreciate the importance of reading the pages and pages of info. Spent a full 2 weeks reading before i rooted my nexus one. Shame, i think my nexus is feeling left out! Might flash something on that again before the xoom to remind me of what i'm doing!
Click to expand...
Click to collapse
Cm7 is always a good one to remind you how to do things
Sent from my Xoom using XDA Premium App
iammodo said:
Hello all uk wifi xoomers
Have you noticed the motoblur applications when you go to manage applications> all?
Have you noticed your still on 3.0.1
Well flash the us image files.
I bit the bullet and did it.
got the 3.1 update and is so much faster and the browser works so much better/faster
The whole os seems to be faster as well
Also no more motoblur crap.
Also means when the next update comes out you will get it rather then waiting
I recommend it to any uk xoomer.
Only works on wifi do not try on 3g
Sent from my Xoom
Click to expand...
Click to collapse
The only "motoblur crap" I see on my device is "MotoBlur Services", taking up 32k. There's also a "Motorola location proxy service".
So, deffo no ill effects by flashing with the US image with regards to App Market and other location specific things?
mrgimper said:
The only "motoblur crap" I see on my device is "MotoBlur Services", taking up 32k. There's also a "Motorola location proxy service".
So, deffo no ill effects by flashing with the US image with regards to App Market and other location specific things?
Click to expand...
Click to collapse
I have been able to restore all my apps without any problems. It is the same UK market I believe as I don't have access to US only apps like Google books. There is a shortcut to it but it is not installed and cannot be found on market.
I was hesitant at first but took the dive and I am very happy I did. It is definitely much smoother and faster. Flash 10.3 works flawlessly now. I can play Videos smoothly that I haven't been able to before. Gallery displays pictures correctly. I keep finding improvements everywhere.
blueberet said:
I have been able to restore all my apps without any problems. It is the same UK market I believe as I don't have access to US only apps like Google books. There is a shortcut to it but it is not installed and cannot be found on market.
Click to expand...
Click to collapse
Very strange, but Google Books actually really is installed. When you root your device and install Titanium Backup, you can see it is 'frozen'. As soon as you 'unfreeze' it, it will function correctly and you will see it in the app drawer.
seakins said:
Thanks for the how-to-do guide, really spelt it out!
Click to expand...
Click to collapse
No worries, I spent a few days trying to figure it out myself so thought I'd share the wealth.
mbroeders said:
Very strange, but Google Books actually really is installed. When you root your device and install Titanium Backup, you can see it is 'frozen'. As soon as you 'unfreeze' it, it will function correctly and you will see it in the app drawer.
Click to expand...
Click to collapse
Anyway to unfreeze it without root?
Sent from my Xoom using XDA Premium App
Finally bit the bullet and flashed the US firmware. Used the instructions in this thread and no probs.
Moments after my xoom rebooted, the 3.1 update was ready to install
All installed and happy
I'm really tempted to do this but is there any way to flash the US system image and not lose data? I really don't want to have to mess around getting all my apps/games back.
Sent from my XOOM using XDA Premium App
baggy247 said:
I'm really tempted to do this but is there any way to flash the US system image and not lose data? I really don't want to have to mess around getting all my apps/games back.
Sent from my XOOM using XDA Premium App
Click to expand...
Click to collapse
No, you have to wipe data or you will brick it.
when I changed my xoom for another xoom because the first was broken I re-installed appbrain and logged back in with my gmail account and all the apps were listed to download very quickly and easily through appbrain
dont know if that's any help to you...
baggy247 said:
I'm really tempted to do this but is there any way to flash the US system image and not lose data? I really don't want to have to mess around getting all my apps/games back.
Click to expand...
Click to collapse
The market should auto-install all your old apps, but you'll need to root and use something like titanium backup to carry over the app settings. No idea how you do this, but I've been told that this is one of the reasons for rooting.
The stock image for the NExus 7.
Will it be possible for devs to make a CWM flashable stock rom from this? Or one used with Odin? Can Odin even be used with the Nexus 7?
Odin is a Samsung tool that can only be used on samsung devices.
Factory images for nexus devices are available straight from google usually on the day any update is released, these can be flashed with fastboot which is a small exe/shell program that you can download by downloading the free android SDK and using that to download platform tools. It will all become easier in time when devs get hold of this device as I can almost guarantee there will be some kind of toolkit released (think the Galaxy Nexus toolkit or Galaxy S III toolkit) that will allow you to do all this kind of stuff with a few simple selections and buttons.
DarkRyoushii said:
It will all become easier in time when devs get hold of this device as I can almost guarantee there will be some kind of toolkit released (think the Galaxy Nexus toolkit or Galaxy S III toolkit) that will allow you to do all this kind of stuff with a few simple selections and buttons.
Click to expand...
Click to collapse
Thanks, yeah I read some about it yesterday and downloaded it. I have the SDK and have used ADB but not extensively. I saw the factory image came with .sh files for flashing, which I've never used.
I'm sure you're right. By the time I need to use it it will probably be a lot easier.
.sh files are pretty much batch files but for linux machines, they allow (but not limited to) scripting. The sh file is not needed to flash your device and all that's needed is fastboot. Trust me, it's great knowing how to flash without the use of a toolkit and once you've done it once or twice, it becomes infinitely easier for other devices.
Loaded this image on my Nexus 7 today on Windows.
Once you have the fastboot adb utility, the flash-all.bat file in the archive will flash the image for you.
Do not attempt to flash the internal .zip file using recovery. It won't work!! Using the fastboot utility and the included batch files is the ONLY way you can flash this image!!
Be very aware that this image will do a FULL factory wipe and format of your device so make sure you have backed up your apps & data (Bad Google!!) - a particular pain in the ass since there is no external SD Card to copy things to before it goes ahead wipes the entire internal memory. It will also remove any books and customizations you had. Copy any data you want to keep off of the device before applying this update. It will disappear after the flash. You have been warned.
On the plus side once you get your stuff reinstalled and downloaded to the tablet, everything works very smooth.
Unlawful said:
.sh files are pretty much batch files but for linux machines, they allow (but not limited to) scripting. The sh file is not needed to flash your device and all that's needed is fastboot. Trust me, it's great knowing how to flash without the use of a toolkit and once you've done it once or twice, it becomes infinitely easier for other devices.
Click to expand...
Click to collapse
.sh files are more generally scripts run in any BASH terminal/POSIX related operating system, so you'll see them on more than Linux (OS X and Solaris, for example). But it's much better to use command line tools than to rely on a toolkit, I agree.
penguinjoe said:
Loaded this image on my Nexus 7 today on Windows.
Once you have the fastboot adb utility, the flash-all.bat file in the archive will flash the image for you.
Do not attempt to flash the internal .zip file using recovery. It won't work!! Using the fastboot utility and the included batch files is the ONLY way you can flash this image!!
Be very aware that this image will do a FULL factory wipe and format of your device so make sure you have backed up your apps & data (Bad Google!!) - a particular pain in the ass since there is no external SD Card to copy things to before it goes ahead wipes the entire internal memory. It will also remove any books and customizations you had. Copy any data you want to keep off of the device before applying this update. It will disappear after the flash. You have been warned.
On the plus side once you get your stuff reinstalled and downloaded to the tablet, everything works very smooth.
Click to expand...
Click to collapse
You can flash that .zip using the stock recovery, but otherwise it's a bad idea.
The rest of this post isn't quite correct. Using the fastboot utility is a way of flashing this image-- the included bash/shell script files are helper tools designed to make things more convenient. It's hardly a case of "Bad Google" -- if you don't want the hassle, wait for the OTA.
You can flash preserving data by putting your device into fastboot and running (after extracting everything out of the .tar):
fastboot flash bootloader <path-to-bootloader.img>
fastboot flash system <path-to-system.img>
You don't have to push either userdata.img or recovery.img-- those will wipe what the names correspond to.
Rirere said:
You can flash that .zip using the stock recovery, but otherwise it's a bad idea.
Click to expand...
Click to collapse
doesn't help you if you have TWRP installed on grouper (I did).
Rirere said:
The rest of this post isn't quite correct. Using the fastboot utility is a way of flashing this image-- the included bash/shell script files are helper tools designed to make things more convenient. It's hardly a case of "Bad Google" -- if you don't want the hassle, wait for the OTA.
You can flash preserving data by putting your device into fastboot and running (after extracting everything out of the .tar):
fastboot flash bootloader <path-to-bootloader.img>
fastboot flash system <path-to-system.img>
You don't have to push either userdata.img or recovery.img-- those will wipe what the names correspond to.
Click to expand...
Click to collapse
Bro, is this documented anywhere? Anywhere at all? I got this image straight from Google along with their instructions on how to install it. There was absolutely no mention whatsoever of this.
Their instructions say nothing about extracting the img files out of the embedded zip file and flashijg them individually. Nor do they say what files are mandatory to be flashed and what isn't. To that I still say "Bad Google" since they documented no such information that allowed me to install this image AND preserve my data/installed apps. I am sure their OTA update wouldn't.
I passed on the information I was given with the image. I am not an android developer. I am an average android user and my post is not meant for android developers who know far more about this than I do. I documented my experiences as an average android user for folks who like me, are also average android users and want to know how to upgrade their ROM without waiting for the OTA. My warnijng is that if the follow the same instructions I was given, they will indeed WIPE THEIR TABLET.
Cheers!
penguinjoe said:
doesn't help you if you have TWRP installed on grouper (I did).
Click to expand...
Click to collapse
Not my problem. You put TWRP there-- you should know how to get it off.
penguinjoe said:
Bro, is this documented anywhere? Anywhere at all? I got this image straight from Google along with their instructions on how to install it. There was absolutely no mention whatsoever of this.
Click to expand...
Click to collapse
Yep. Android Police ran a huge feature on it recently. You could also look in any of the million forum threads that show up at OTA time or ask if it's possible. There's that too.
penguinjoe said:
Their instructions say nothing about extracting the img files out of the embedded zip file and flashijg them individually. Nor do they say what files are mandatory to be flashed and what isn't. To that I still say "Bad Google" since they documented no such information that allowed me to install this image AND preserve my data/installed apps. I am sure their OTA update wouldn't.
I passed on the information I was given with the image. I am not an android developer. I am an average android user and my post is not meant for android developers who know far more about this than I do. I documented my experiences as an average android user for folks who like me, are also average android users and want to know how to upgrade their ROM without waiting for the OTA. My warnijng is that if the follow the same instructions I was given, they will indeed WIPE THEIR TABLET.
Cheers!
Click to expand...
Click to collapse
I'm sorry, but cry me a river/a.k.a. I have zero sympathy for this point of view. OTAs are meant for end-users and are designed not to wipe data. They roll out in stages to keep things simpler for end-users as well, so that early bugs or problems can be caught and rectified quickly. If you didn't want to wait, more power to you, but it's absolutely not Google's fault here-- it's 100% your own.
Because that link you used to download the files-- do you see that URL? It's developers.google.com. Not "averageuser" or "everybody." The instructions and files are there primarily for developers who know what they're doing, which is why Google doesn't send you a newsletter saying "hey, follow the instructions here!" They warned you in the instructions that the default behavior of those instructions is to wipe your data. Yes, the default. Yes, that means you can do other things.
The moment you decided to do this is the moment you took responsibility for what happened. There happen to be "better" ways of getting this OTA without killing data, if that's what you want, which are really:
a) Learn to use the command line tools, which is the best option in the long run if you want to work with ROMs.
b) Wait for a TWRP-modified update zip.
c) Wait for the OTA.
Full stop.
To the asshats that appear to think they know it all - thanks for your input. Not sure what bee crawled up your ass and died there, but thanks for the useful bits of that tirade.
To the others like the OP that have downloaded that image and are attempting to figure out how to install it, my post stands on its own merits. Google's instructions worked just fine for me. The same warning I have given is included in Google's installation instructions - you are installing a full image not an update image.
See Rirere's first post for alternate means of dissecting the installation package and installing without losing your data and apps. If you brick your tablet please feel free to take it up with him.
Cheers!
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
Hello,
Problem:
factory reset my Droid RAZR M with the hope to resolve in-call audio problems (very low ear piece volume at full). When I rebooted the phone the Welcome screen appeared asking for a language choice. Chose english US. The Message: "Please wait, This may take a few minutes" appeared with a spinning icon. But nothing else ever happens. The phone never moves beyond this selection.
I have android-sdk (Linux setup) installed on my computer in order to use the suite of tools like fastboot and adb. The tools work, in that I can see the phone, pull data, upload to the phone and even get a command shell on the phone. However in order for adb to recognize the phone I have to put the phone in "BT Tools" mode. In "AP fastboot" mode fastboot sees the phone. As far as I remember USB debugging was turned on.
I do not have a recovery image installed.
The phone has Kitkat 4.4.2 ver 183.46.10 and is rooted with TowelRoot. I just unlocked the bootloader today via motoapocalypse package. Status of the phone is unlocked Code 3
I also removed some unused apps - like NFL and a few other space and bandwidth consuming apps that I will never use.
I'd like to get this phone to work again. Is there any hope?
Please advise and thanks for reading.
You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More
Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Klen2 said:
You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More
Click to expand...
Click to collapse
diordnAMRZAR said:
Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Click to expand...
Click to collapse
You can try using SBF_FLASH or mFastboot-v2 (which has a linux version) to flash the system.img .
SOLVED: [Q] Droid Razr M not fully booting: Help Please
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!
diordnAMRZAR said:
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!
Click to expand...
Click to collapse
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.
ATTACK said:
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.
Click to expand...
Click to collapse
Well I'm happy to have the utility that works. Can thank you enough -- or the creators. Found it also on goggle code after a properly crafted search string. All this for an in-call audio problem that only worsened after I took the phone apart. Still works on speaker mode though so that's good enough -- at low volume. And I learned a few things. One interesting thing: The shell prompt got rewritten to say ${USER}@scorpion_mini/ after flashing the system.img. Pretty sure it only said android prior to re-flashing . And the getprop helper app is a new thing for me.
Feel like a kid all over again exploring this little device.