Using moto-fastboot (thanks, eval- and _unknown), we can flash any developer build unlocked images in Fastboot mode. Thanks to Team Black Hat, we were given a very early developer build with AOSP Gingerbread (mostly). That build was based on GRH55.
This build is pretty dang buggy, but its AOSP applications and such can certainly be harvested for use by devs. If you're just playing around, you'll want to move back to HKTW or stock within 10 minutes. If you want to farm the apps and libs, just mount the system image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basic Information
Code:
Android 2.3
Build number: olympus-eng 2.3 GRH55 eng. w30562.20110119.152615 test-keys
Date: January 19, 2011
System version: 0.0.1.MB680.ATT.en.US
Working
Data and cellular network
All applications (for the most part)
Buggy, weird, or broken
Phone application
Extremely slow!
WiFi broken
GPS
Often reboots
Some elements reflect Blur style, most are AOSP
Installation
Prerequisites
Linux [until moto fastboot is recompiled for Windows]
moto-fastboot (64-bit, 32-bit)
GRH55 boot image
GRH55 system image [[URL="http://www.filesonic.com/file/1297604021/system-grh55.zip"]Mirror]
[/URL]
Unlocked bootloader
Instructions
Commands are the same as the HKTW build flash. Thank _unknown and eval- for making it easy for everyone.
Boot the device into Fastboot mode
Power off device
Press and hold downward volume and power buttons until "Fastboot" appears
Press the upward volume button
Open a terminal window and issue the following commands
Code:
sudo ./moto-fastboot flash boot boot-grh55.smg
sudo ./moto-fastboot flash system system-grh55.smg
sudo ./moto-fastboot -w
sudo ./moto-fastboot reboot
Replace "moto-fastboot" with "moto-fastboot32" if you're on a 32-bit or VMWare system.
Reboot and enjoy!
My brain is gonna explode from all the kickass stuff being posted today!! LOL I hope this day never ends!! Thanks Kenneth!!
Im a newb running linux. I have linux in a virtual box. I downloaded moto-fastboot and the two image files. Now where do I extract these files too in linux? When I run the commands it just says command not found? I have the files on my desktop in linux, how do I direct linux to flash the files too the phone via fastboot through the terminal since it cant find the file?
JayRolla said:
Im a newb running linux. I have linux in a virtual box. I downloaded moto-fastboot and the two image files. Now where do I extract these files too in linux? When I run the commands it just says command not found? I have the files on my desktop in linux, how do I direct linux to flash the files too the phone via fastboot through the terminal since it cant find the file?
Click to expand...
Click to collapse
Make sure to check out eval-'s thread in General. Read up there.
To answer your questions...
1.) Extract the files to your home folder (for me it was my username, Kenneth)
2.) Right click the moto-fastboot32 (you need 32-bit) and click Properties... change permissions to read/write
Now give it a go.
kennethpenn said:
Make sure to check out eval-'s thread in General. Read up there.
To answer your questions...
1.) Extract the files to your home folder (for me it was my username, Kenneth)
2.) Right click the moto-fastboot32 (you need 32-bit) and click Properties... change permissions to read/write
Now give it a go.
Click to expand...
Click to collapse
So I extracted both img files for the GB build too my User name folder along with the moto-fasboot32 and changed permissions. When I run the commands exactly how they are I get ./moto-fastboot command not found. I know Im missing something easy.
JayRolla said:
So I extracted both img files for the GB build too my User name folder along with the moto-fasboot32 and changed permissions. When I run the commands exactly how they are I get ./moto-fastboot command not found. I know Im missing something easy.
Click to expand...
Click to collapse
You need to use ./moto-fastboot32 not ./moto-fastboot.
kennethpenn said:
You need to use ./moto-fastboot32 not ./moto-fastboot.
Click to expand...
Click to collapse
OMG, thank you. I knew it was something easy, LOL.
JayRolla said:
OMG, thank you. I knew it was something easy, LOL.
Click to expand...
Click to collapse
No problem. I edited the instructions for clarity.
So this is why you aren't responding to me...shame Kenneth smh
Gutterball said:
My brain is gonna explode from all the kickass stuff being posted today!! LOL I hope this day never ends!! Thanks Kenneth!!
Click to expand...
Click to collapse
It's like an early Christmas, then in a few days we get fireworks, what next, overclocking xD imagine running a rom optimized for dual core at even 1.4GHz a core, sure your battery will die faster than road kill, but hey, imagine the games that would be possible, IMAGINE THE WEBTOP THAT WOULD BE POSSIBLE!!! Excuse me while I go dance like a little girl from all this happy news lol
Korey_Nicholson said:
So this is why you aren't responding to me...shame Kenneth smh
Click to expand...
Click to collapse
Lol, he's calling in sick tomorrow
Sent from my MB860 using XDA App
so this is native? no moto influences or accents??
when can we expect cwm version or this ?
kennethpenn said:
Using moto-fastboot (thanks, eval- and _unknown), we can flash any developer build unlocked images in Fastboot mode. Thanks to Team Black Hat, we were given a very early developer build with AOSP Gingerbread (mostly). That build was based on GRH55.
This build is pretty dang buggy, but its AOSP applications and such can certainly be harvested for use by devs. If you're just playing around, you'll want to move back to HKTW or stock within 10 minutes. If you want to farm the apps and libs, just mount the system image.
Basic Information
Code:
Android 2.3
Build number: olympus-eng 2.3 GRH55 eng. w30562.20110119.152615 test-keys
Date: January 19, 2011
System version: 0.0.1.MB680.ATT.en.US
Working
Data and cellular network
All applications (for the most part)
Buggy, weird, or broken
Phone application
Extremely slow!
WiFi broken
GPS
Often reboots
Some elements reflect Blur style, most are AOSP
Installation
Prerequisites
Linux [until moto fastboot is recompiled for Windows]
moto-fastboot (64-bit, 32-bit)
GRH55 boot image
GRH55 system image [[URL="http://www.filesonic.com/file/1297604021/system-grh55.zip"]Mirror]
[/URL]
Unlocked bootloader
Instructions
Commands are the same as the HKTW build flash. Thank _unknown and eval- for making it easy for everyone.
Boot the device into Fastboot mode
Power off device
Press and hold downward volume and power buttons until "Fastboot" appears
Press the upward volume button
Open a terminal window and issue the following commands
Code:
sudo ./moto-fastboot flash boot boot-grh55.smg
sudo ./moto-fastboot flash system system-grh55.smg
sudo ./moto-fastboot -w
sudo ./moto-fastboot reboot
Replace "moto-fastboot" with "moto-fastboot32" if you're on a 32-bit or VMWare system.
Reboot and enjoy!
Click to expand...
Click to collapse
It says "System version: 0.0.1.*MB680*.ATT.en.US", which should be "System version: 0.0.1.*MB860*.ATT.en.US", had to point that out lol
jahizen said:
so this is native? no moto influences or accents??
Click to expand...
Click to collapse
There are a few. Simple edits can take them out. Mostly AOSP, though. This is clearly their first (or one of the first) engineering build.
has fastboot been recompiled for windows?
Dubee24 said:
has fastboot been recompiled for windows?
Click to expand...
Click to collapse
No. Someone needs to do it using Cygwin. Best info: http://groups.google.com/group/android-porting/browse_thread/thread/4990ffe551844860?pli=1&fwc=1
anyone know what is the code group CGXX.smg for this boot-grh55.smg??
I'm getting the following,
Code:
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.003s
phone displays
Failed to process command download :14000000 error(0x6)
is there a solution to this?
you need to flash it on linux
Related
DISCLAIMER:
1) You are doing this at your own risk.
2) Educate yourself first and try this ONLY if you feel comfortable with modifying with your phone.
3) If you break your phone it is not my fault nor is it my responsibility to fix your phone.
Things could go wrong but they shouldn't if you follow the directions and have some general knowledge of Android.
##############################
Go from this:-------------------------------------------------To This:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----------
##############################
Things needed:
ADB/Fastboot knowledge - HERE and HERE
RGB565Converter v0.3c - Thanks to DeToX-cz!
UPDATE: You must have the engineering bootloader flashed for access to splash1. Follow the steps here to flash the S=OFF bootloader. -Thanks to jcase
Instructions:
Find an or create an image (.png, .bmp, .jpg, or .gif -- 320x480 is preferrable)
Open RGB565 Converter
Ensure that "To RGB565 (binary)" tab is selected
Click "Open Image", select your image
Click "Convert to RGB565" (RGB565 Converter will make your image 320x480 if it is not already)
CLOSE RGB565 CONVERTER
Reboot phone into Fastboot using this command: adb reboot bootloader
OR Button combo: SEND/CALL + END/POWER
Flash image using this command: fastboot flash splash1 <your_image_name>.rgb565
Reboot phone using this command: fastboot reboot
OR fastboot oem powerdown if not then remove your battery
View the results of your hard work.
Enjoy!
As of right now there is no way to read the splash1 partition to back it up short of some kind of kernel mod to partition splash1 from NAND as a new MTD. At least that's how I understand it, please correct me if I'm wrong.
You must flash the S-OFF BOOTLOADER for this to work.
You can use the RGB565Converter tool to flash your image successfully without needing to type commands.
Below is another method used to keep your phone from rebooting unexpectedly during the process:
joshw0000 said:
I tried using the "Flash Splash1" button that someone had posted earlier and I almost **** myself. I think my phone tried to load the file I originally used to root it. I was getting really nervous so I pulled the battery and, to my relief, it powered on and it booted normally. I'm sure that method works but I'm scared of it now.
I tried the original instructions and it rebooted my phone before I was ready so I did this in the command prompt (this was mentioned on the first page of posts):
cd C:\android-sdk-windows\tools
adb shell
su
reboot bootloader
fastboot flash splash1 <copy and paste file name here>
fastboot reboot
Of course this will only work if you've downloaded the program, converted your picture and placed it in the tools directory of SDK.
Worked great for me. I couldn't be happier!
Click to expand...
Click to collapse
didnt seem to work for me, but im not rooted, ill try this with my brothers rooted phone in a bit and repioret back
Wow that worked great! Thanks
Reboot phone into Fastboot (Power down, hold Send press and hold Power)
Click to expand...
Click to collapse
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
ch4sethe5un said:
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
Click to expand...
Click to collapse
no, Hold Call button and end button to get into fastboot
and this is ONLY FOR ROOTED PHONES
thanks
thanks i will try it out. Im using ivan's 0.7
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
ch4sethe5un said:
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
Click to expand...
Click to collapse
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
there should be an option to go to HBOOT menu and then into recovery and reboot from there.
I used this one:
Great tutorial. Thanks!
Here's mine if someone likes it they are free to use it.
+1 rep (if only we could do that). I was looking for something like this. Thanks!
t2noob said:
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
Click to expand...
Click to collapse
I did a battery pull myself too lazy to go into recovery from hboot. My phone did not explode after doing a battery pull so it "should" be safe however do so with caution.
moved thread by request of OP.
Best regards,
Flar
Ive learned that battery pull is the easyiest way,
As a fan of FFXIII, I could not pass up the opportunity to do this.
[Taking Requests also ]
Maybe we should come up with a thread so people can post all boot images and animations in one place, no?
Just remember to convert it like mentioned in the first post
Here is one(as a fan =] ):
Was just thinking about changing and found this. Thanks.
Awesome!!!
Thanks for the tutorial.
Worked great!
BIG THANKS TO MUR4IK FOR THIS TOOL! Be sure to donate to him and support his work!
Cannot get the builder to run or use Linux/Mac? Solution here!
In this guide I will be showing you how to resize your data + system partitions for more/less space.
Things you will need:
LG GT540 w/ A Fastboot ROM installed
LG drivers and Fastboot/ADB drivers installed
Windows (with .NET Framework 3.5 SP1 installed. If you have trouble launching the program, (re)install .NET 3.5 SP1. Also this tool will not work with Wine on Linux.)
Your phones USB cable.
WARNING: MAKE SURE TO NANDROID BACKUP YOUR ROM BEFORE CHANGING THE PARTITION SIZES! YOU MAY NEED IT LATER. ALSO, THIS TOOL DOES NOT REMOVE RECOVERY.
First of all, grab the SwiftBootloaderBuilder.zip from http://kulkoff.com/swift/ or from here.
(Mur4ik's site is recommended)
Next, put your phone into Fastboot Mode (Camera+Power)
Extract the files to your Desktop using any archiving program. Then go to the folder you extracted. Right Click and Select 'Run as Administrator'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will see a window like this pop up:
Now we can alter the partition sizes. If you want the same effects as Mur4ik's 234MB DATA KDZ, choose 150MB system, and the data column will change accordingly. If you want a bit more system space (eg. To run airbus360's LG Optimus One ROM) Select 190 system. Basically, adjust the settings to how you want. My recommendations are:
For SwiftDroid, joe.stone AOSP, airbus360 AOSP, EleganceSwift, MMXTREM 2.1 Lite, Quarx Black ROM: 150 system 234 data
For airbus360 Optimus One: 190 system 194 data
For stock 2.1: 250 system 134 data
Once you have decided on the size you want, hit 'Flash New Bootloader' and confirm you really want to do this. You will get a 'Done' message and then click OK. Select 'Wipe Data' and then Reboot Device. After you click reboot, hold down HOME until recovery pops up.
Now you have two choices. Either install a new ROM from scratch, or restore your nandroid backup you made earlier.
This tool also has the option to remove fastboot and recovery from the device, so you can return to stock firmware, and possibly use regular LG updates again.
Thats it!
If you've got any questions, PM me or reply to the thread.
Also, don't forget to say
if I helped!
Anyone with WinXP SP3 32-bit has got it working successfully?? I still can't make it work. Resizing, removing fastboot & recovery doesn't work for me.
not sure it works on 32bit. it was tested by mur4ik using a 64bit windows7 computer.
bs828 said:
not sure it works on 32bit. it was tested by mur4ik using a 64bit windows7 computer.
Click to expand...
Click to collapse
It works on 32bit Win7
Sent from my GT540 using XDA Premium App
Works perfectly for me on win7 32bit! thanks for making this!!!
tejasdj12 said:
Anyone with WinXP SP3 32-bit has got it working successfully?? I still can't make it work. Resizing, removing fastboot & recovery doesn't work for me.
Click to expand...
Click to collapse
I have only tried on Windows 7, but i'll try it on my netbook soon (that runs XP)
Working fine for me (XP SP3 w/ .NET 3.5 SP1) No issues at all, also partitions resize ok too.
Hi. Thats should be added in header that this "tool" has a requirements MS .NET frameworks 3.5 SP1 and adove.
Mur4ik,
Because this tool can save the bootloader instead of flashing it, would it work to save the bootloader using the tool in Wine, then flashing it with fastboot (maybe a solution for Linux users) What would the command be to flash this boot bootloader?
Thanks.
effortless. said:
Mur4ik,
Because this tool can save the bootloader instead of flashing it, would it work to save the bootloader using the tool in Wine, then flashing it with fastboot (maybe a solution for Linux users) What would the command be to flash this boot bootloader?
Thanks.
Click to expand...
Click to collapse
Code:
fastboot flash APPSBL your_file_filename.mbn
Mur4ik said:
Code:
fastboot flash APPSBL your_file_filename.mbn
Click to expand...
Click to collapse
Thanks, I will try later!
EDIT: Doesn't matter, .NET 3.5 SP1 wont install, also using Winetricks didn't help. But what I might do is, create a load of bootloader files (on my Windows machine) and then upload them, so users can flash w/ fastboot.
Anyone knows how to get fastboot on fresh stock ROM without that KDZ stuff? Coz I'd just bricked my phone (dead phone), but the LG people in India are too generous to fix it in two hours.
I won't take any risks with KDZ. But I'm missing Swiftdroid and other stuff. Please can someone tell how do I install fastboot somehow without using KDZ?
tejasdj12 said:
Anyone knows how to get fastboot on fresh stock ROM without that KDZ stuff? Coz I'd just bricked my phone (dead phone), but the LG people in India are too generous to fix it in two hours.
I won't take any risks with KDZ. But I'm missing Swiftdroid and other stuff. Please can someone tell how do I install fastboot somehow without using KDZ?
Click to expand...
Click to collapse
You could root your phone then use root explorer and copy the flash image file to the bin folder then run the command mur4ik posted in this thread but change fastboot to flash_image run the command in terminial that should work.
This is the command
su
flash_image APPSBL your_file_filename.mbn
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
flash_image APPSBL your_file_filename.mbn
Click to expand...
Click to collapse
Which file should I flash? The one that's created by Swift Bootloader Builder? Will it enable fastboot? (ATM I don't have fastboot in my phone)
tejasdj12 said:
Anyone knows how to get fastboot on fresh stock ROM without that KDZ stuff? Coz I'd just bricked my phone (dead phone), but the LG people in India are too generous to fix it in two hours.
I won't take any risks with KDZ. But I'm missing Swiftdroid and other stuff. Please can someone tell how do I install fastboot somehow without using KDZ?
Click to expand...
Click to collapse
You might be able to flash it using flash_image. But either: flash_image may not be able to access the appsbl partition or it may not be able to be changed 'on the fly' so to speak. You can try this, not sure if it will work, root is needed, not sure if it will brick your phone, I have not tried this method.
Download either:
150 system 234 data
250 system 134 data
and also download flash_image from here
Put the .mbn and flash_image file on your SDCard.
Open a terminal emulator and type the following:
Code:
su (press allow when prompt comes up)
cd /sdcard/
chmod +x ./flash_image (if this doesn't work, try chmod +x flash_image)
./flash_image appsbl appsboot_150_234_64.mbn (or appsboot_250_134_64.mbn)
sync
Now try entering fastboot and flash recovery. In theory, it should work.
oh snap, Eoghan beat me to it
@eoghan and effortless.
Thanks for your help, I'll try that later.
EDIT: One doubt, I don't think it's possible to resize partitions while using them.
Lets hope it works, then once at 2.1, there is no need for KDZ anymore (sort of)
tejasdj12 said:
@eoghan and effortless.
Thanks for your help, I'll try that later.
EDIT: One doubt, I don't think it's possible to resize partitions while using them.
Click to expand...
Click to collapse
It will resize, as the partition table is only changed on boot (as far as I know)
Nope, it says "Can't find appsbl partition"
tejasdj12 said:
Nope, it says "Can't find appsbl partition"
Click to expand...
Click to collapse
It might be case sensitive, try APPSBL instead
READ THE WARNING
READ THE ENTIRE POST
DETAILED INSTRUCTIONS AFTER FILE
I am not responsible for bricked devices, firings due to the alarm not going of, thermonuclear war caused by a missed phone call or anything that goes wrong because of this. Try at your own risk (it'll work if you do it right)
Click to expand...
Click to collapse
I just finished flashing the 4.3 Factory images without losing user data.
I was previously running 4.2.2 Stock unrooted, with an unlocked bootloader.
You can do this simply by taking the .sh or .bat file they provide and removing the
Code:
-w
flag from the
Code:
fastboot update
command
This is my modified flash-all.sh for a mac:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-jwr66v.zip
Prerequisites:
1. Download the file for flashing from here.
2. Make sure your bootloader is unlocked. If it is not, you will have to unlock it which WILL WIPE YOUR DEVICE. Wait for the OTA or make a backup somewhere if you like your data. If you want to unlock the bootloader use:
Code:
fastboot oem unlock
Detailed steps:
1. Extract the downloaded tgz. You should have the following files: bootloader-mako-makoz20i.img, flash-all.bat, flash-all.sh, flash-base.sh, image-occam-jwr66v.zip and radio-mako-m9615a-cefwmazm-2.0.1700.84.img.
2. Depending on your platform open either the flash-all.bat (Windows) or the flash-all.sh (UNIX/Linux/Mac) file in a text editor, and remove the -w flag from the last line.
3. Open a terminal, connect your device, enable USB Debugging and then:
Code:
adb reboot bootloader
sh flash-all.sh
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: This will probably not work if you're running custom recoveries and/or custom ROMs. Having a rooted stock ROM should not be a problem, though you will almost definitely lose root
Is the headphone output fixed? Does it sound louder than before?
vickpick said:
Is the headphone output fixed? Does it sound louder than before?
Click to expand...
Click to collapse
There doesn't seem to be any difference to me, but I have fairly crappy headphones.
Raghav Sood said:
There doesn't seem to be any difference to me, but I have fairly crappy headphones.
Click to expand...
Click to collapse
Okay, just making sure, lol. I have the same experience and I was just wondering if I screwed up something while flashing. Thanks!
Raghav Sood said:
I just finished flashing the 4.3 Factory images without losing user data.
I was previously running 4.2.2 Stock unrooted, with an unlocked bootloader.
You can do this simply by taking the .sh or .bat file they provide and removing the
Code:
-w
flag from the
Code:
fastboot update
command
WARNING: This will probably not work if you're running custom recoveries and/or custom ROMs. Having a rooted stock ROM should not be a problem, though you will almost definitely lose root
Click to expand...
Click to collapse
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Please make a tutorial more specific
Triune said:
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Click to expand...
Click to collapse
You'll have to ensure a couple of things:
Extract the tgz. You'll end up with a bunch of img, sh, zip and bat files. Depending on whether you're on Windows or Mac or Linux, you're going to want to run the flash-all.sh or flash-all.bat file. DO NOT RUN IT RIGHT AWAY. First edit it as shown in the Opening Post.
Also make sure that fastboot is in your PATH variable (you'll get an error saying fastboot is not a command if it isn't)
javier13javier said:
Please make a tutorial more specific
Click to expand...
Click to collapse
Editing the OP with more detailed instructions now
Triune said:
I am sorry for the noob question, but I keep getting an "installation aborted" message when trying to flash the factory image. It's a .tgz file and in the past, i've only flashed .zip's. How do I flash that file?
Thanks
Click to expand...
Click to collapse
After unzipping with 7zip for example, you should have available
image-occam-jwr66v.zip
and other files like bootloader-mako-makoz20i.img and radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Raghav Sood said:
You'll have to ensure a couple of things:
Extract the tgz. You'll end up with a bunch of img, sh, zip and bat files. Depending on whether you're on Windows or Mac or Linux, you're going to want to run the flash-all.sh or flash-all.bat file. DO NOT RUN IT RIGHT AWAY. First edit it as shown in the Opening Post.
Also make sure that fastboot is in your PATH variable (you'll get an error saying fastboot is not a command if it isn't)
Click to expand...
Click to collapse
What do you exactly mean with make fastboot variable? I keep getting the fastboot error.
Infinite104 said:
What do you exactly mean with make fastboot variable? I keep getting the fastboot error.
Click to expand...
Click to collapse
fastboot is part of the developer tools, and Google assumes you have it in your PATH. The Cyanogen Wiki has a great page on how to set that up here
RASTAVIPER said:
After unzipping with 7zip for example, you should have available
image-occam-jwr66v.zip
and other files like bootloader-mako-makoz20i.img and radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Click to expand...
Click to collapse
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Just a heads up, you have to unzip twice before u get to flash.bat
TGZ, then TAR.
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
Triune said:
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Click to expand...
Click to collapse
no, you copy all the files into the fastboot folder (iincluding modified bat or sh), then run the bat or sh
Oh and phone should be in download mode and connected.
you don't use the recovery, just press your power down and power and connect when the black screen comes up.
vickpick said:
Just a heads up, you have to unzip twice before u get to flash.bat
TGZ, then TAR.
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
no, you copy all the files into the fastboot folder (iincluding modified bat or sh), then run the bat or sh
Oh and phone should be in download mode and connected.
you don't use the recovery, just press your power down and power and connect when the black screen comes up.
Click to expand...
Click to collapse
That's the difference, i'm in a mac. I don't have a fastboot folder. I wish Google would just release flashable zips. Smh
Triune said:
I've extracted, but what i'm not understanding up to this point is how to flash it. Do you re-zip it then flash it through the stock recovery?
Click to expand...
Click to collapse
Check this:
- YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
- ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
- Launch command prompt (start --> run --> "cmd")
- type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\sdk\platform-tools"
- Type in the command prompt each step one at a time
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-jwr66v.zip"
Will this work if we're on a stock 4.2.2 ROM but with LTE changes (older radio, edited build.prop and soc file?)
Triune said:
That's the difference, i'm in a mac. I don't have a fastboot folder. I wish Google would just release flashable zips. Smh
Click to expand...
Click to collapse
On a mac you should also have fastboot-mac in addition to fastboot.
Replace fastboot in the description with fastboot-mac and you shouldn't get any error messages
bioyuki said:
Will this work if we're on a stock 4.2.2 ROM but with LTE changes (older radio, edited build.prop and soc file?)
Click to expand...
Click to collapse
Just tested, it works fine.
RASTAVIPER said:
Check this:
- YOU MUST HAVE ADB & USB Driver for the device (I used the SDK file from google and PDAnet)
- ENABLE USB Debugging via Developer settings (press the build button 7 times to activate it the "settings --> about phone --> Build Number"
- Launch command prompt (start --> run --> "cmd")
- type in command prompt "cd directory where you have the adb & fast boot" for example here is mine "cd C:\Users\sdk\platform-tools"
- Type in the command prompt each step one at a time
"fastboot flash bootloader bootloader-mako-makoz20i.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-jwr66v.zip"
Click to expand...
Click to collapse
Thats the same of deleting the -w and run the .bat on windows.
EDIT: Ok guys, this will work for windows (you have to install adb on your computer and have bootloader unlocked)
1- Remove the -w from the bat (with any editor), that came with the zip.
2- On cmd put adb reboot bootloader
3- Run the modified bat that dont have the -w, just wait and you will have 4.3.
Proof:
For me I had a custom recovery installed and custom rom, so at first I didn't wipe data. It did not boot. So I flashed twrp, and wiped data, not personal data though, and it booted.
Unpacking, Editing, Packing ROMS GUIDE - Host Zero
First download the tools from the link below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. system.img
2. system.new.dat
1.Unpacking Repacking system.img
1. Paste your system.img in tools folder
2. Open cmd.exe
3. Type:
Code:
mkdir <your_folder_name>
ImgExtactor <raw_sparse.img> system -i
ex: ImgExtactor system.img system -i
4. Now open your folder you have created, you can find your <raw_image> has been extracted.
5. Now edit the files in system folder as your convenience.
6. Now open properties of folder you have created see the size of folder.
7. Now lets pack the image back, open the minimized command window.
Code:
make_ext4fs -s -l <size_of_your_folder+100>M -a system <name_of_packing_image>.img <your_folder_name>/
ex: make_ext4fs -s -l 512M -a system my_new_system.img system/
8. Done, enjoy!
2.Unpacking Repacking system.new.dat
1. Paste your system.new.dat, system.transfer.list and file_contexts in tools folder.
2. Open cmd.exe
3. Type:
Code:
sprs2ext system.transfer.list <name_of_system>.new.dat
ex: sprs2ext system.transfer.list system.new.dat
4. Now again type:
Code:
mkdir <your_folder_name>
ImgExtactor <raw_sparse.new.img> system -i
ex: ImgExtactor system.img system -i
5. Now open folder you have created and you will find the system.new.dat has been extracted.
6. Edit the extracted files.
7. Open properties of the extracted folder and check the size of folder
7. Now open minimized command window.
Code:
make_ext4fs -T 0 -S file_contexts -l <size_of_folder+100>M -a system <name_of_packing_image>.img <your_folder_name>/
ex: make_ext4fs -T 0 -S file_contexts -I 512M -a system my_new_system.img system/
8. Now again type:
Code:
rimg2sdat <your_raw_image>.img
ex: rimg2img my_new_system.img
9. Done! enjoy.
CLICK HERE TO DOWNLOAD TOOLS
Thank you very much.
You refresh the xda University.
I hope the University becomes more active.
We really need more guides to master android OS.
Sent from my SM-N910P using Tapatalk
I tried as rules mention on this thread. unpack was succeed. when I repack, here is the problem:
1. repack was succeed, but when I flash into my phone by spf tools, my phone was stuck at mi.com logo.
2. when I mount new system.img was created into DiskInternals Linux Reader, the file knowing as uknown file.
repack was succeed, but unable to use.
how to fix it?
A useful guide! Thanks!
Sent from my Sony Xperia Z3 Compact using XDA Labs
kevin mitnick said:
I tried as rules mention on this thread. unpack was succeed. when I repack, here is the problem:
1. repack was succeed, but when I flash into my phone by spf tools, my phone was stuck at mi.com logo.
2. when I mount new system.img was created into DiskInternals Linux Reader, the file knowing as uknown file.
repack was succeed, but unable to use.
how to fix it?
Click to expand...
Click to collapse
hey a bit late but i may help you.
Causes for this:
1. May be your rom is odex.
2. May be you are using OTA Update or Patch instead of full rom.
3. Applying more size while building .img
4. make_ext4fs dosent support all kind of roms. it only supports roms based on ICS, JB, KK... but i dont know how google builds factory images then.
Anyways a alternative.
Flash a full stock or custom rom into your device (with root access and adb support)
connect your device
type in cmd:
adb shell
su
(grant permissions on your device)
ls -al /dev/block/platform/*/by-name
now you will get your PMT table (Partition Management Table.)
ex: system ---> /dev/block/mmcblk07
and other partition information also.
now make system.img using adb.
dd if=/partitionnumber of=/sdcard/system.img
ex: dd if=/dev/block/mmcblk07
now you can find fastboot flashable system.img in your sdcard.
do rest with other partitions also. (boot partition manadatory).
enjoy.
Ticklefish said:
A useful guide! Thanks!
Sent from my Sony Xperia Z3 Compact using XDA Labs
Click to expand...
Click to collapse
Thankyou sir for encouraging.
Ticklefish said:
A useful guide! Thanks!
Sent from my Sony Xperia Z3 Compact using XDA Labs
Click to expand...
Click to collapse
Your Welcome sir.
HostZero said:
hey a bit late but i may help you.
Causes for this:
1. May be your rom is odex.
2. May be you are using OTA Update or Patch instead of full rom.
3. Applying more size while building .img
4. make_ext4fs dosent support all kind of roms. it only supports roms based on ICS, JB, KK... but i dont know how google builds factory images then.
Anyways a alternative.
Flash a full stock or custom rom into your device (with root access and adb support)
connect your device
type in cmd:
adb shell
su
(grant permissions on your device)
ls -al /dev/block/platform/*/by-name
now you will get your PMT table (Partition Management Table.)
ex: system ---> /dev/block/mmcblk07
and other partition information also.
now make system.img using adb.
dd if=/partitionnumber of=/sdcard/system.img
ex: dd if=/dev/block/mmcblk07
now you can find fastboot flashable system.img in your sdcard.
do rest with other partitions also. (boot partition manadatory).
enjoy.
Click to expand...
Click to collapse
thanks for respon @HostZero so much lessons and knowledge about this.
I'll try..report asap
kevin mitnick said:
thanks for respon @HostZero so much lessons and knowledge about this.
I'll try..report asap
Click to expand...
Click to collapse
This method is know as dumping method thanks to dd and su in android devices.
Cmd.exe not work on windows 7 32bit
?
sent from Xperia™ SP | Android 6.0.1
It seems to me that the permissions would be lost when they are dumped from system.img via this method. Are you seeing the selinux contexts preserved?
hamed24 said:
Cmd.exe not work on windows 7 32bit
sent from Xperia™ SP | Android 6.0.1
Click to expand...
Click to collapse
No problem. Open your tools folder in full screen. now below empty white space click (Shift + RightClick) then select Open Command Window Here.
Done!
HostZero said:
No problem. Open your tools folder in full screen. now below empty white space click (Shift + RightClick) then select Open Command Window Here.
Done!
Click to expand...
Click to collapse
Thanks for your help,that's work
Can you take screenshot from your cmd and typed codes, I'm beginner and confused some codes ?
sent from Xperia™ SP | Android 6.0.1
hamed24 said:
Thanks for your help,that's work
Can you take screenshot from your cmd and typed codes, I'm beginner and confused some codes
sent from Xperia™ SP | Android 6.0.1
Click to expand...
Click to collapse
Sorry bro I have recently shifted to Ubuntu14.04 for learning building. Read guide properly you will understand more. I have even provided examples as well as commands. and commands depends in each system folder.
hamed24 said:
Cmd.exe not work on windows 7 32bit
?
sent from Xperia™ SP | Android 6.0.1
Click to expand...
Click to collapse
Hi hamed24
Start-->run--> cmd.exe didn´t work? but using the right Mousebutton is okay?
Seems that Windows has lost the C:\Windows\system32 entry in the PATH Variable... easy to fix...
1. Press "Windows-Sign" Key and Break at the same time (it´s the same as rightclick on the Computer-Icon on the Desktop), click on Advanced System Settings.
2. Inside the new Window, click on Environment Variables, a new window opens. Now the lower part is the important one... look for PATH and doubleclick it.
3. At the end of the line, check if there is a ";" (without quotes). That seperates the different entries.... if there´s one there ... ok, place cursor at the end and enter C:\WINDOWS\SYSTEM32;
4. Hit ENTER, close all Windows, log off and on again.... and try again, should work now. If not, go to Start-->Run--> and type C:\WINDOWS\SYSTEM32\CMD.EXE and there you are
regards...
daywalker386
Thanks :3 Many thanks!!!!!! Very helpful thread!!!!!!
On <size_of_your_folder+100>M
For ex,
The folder size is 924MB, + 100MB=1024MB.
Is it right?
Unexpected argument: system
Hi, is that thread still active?
the tool download link is not working.
Fail could not create Tustarfilesystem
After xiaomi decided to push an update of miui with lollipop, they decided to change partitions and firmware is new too which is bad (as it causes bootloop) if you want to switch to Cyanogenmod 13 which has got official support recently.
So its good to get back on kitkat MIUI to switch to Cyanogenmod.
Let's get started!
THINGS YOU'LL NEED:
1. ADB and Fastboot tools: http://d-h.st/oFLb
2. Stock MIUI kitkat ROM: http://bigota.d.miui.com/V6.7.1.0.K...ICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
3. 7zip (Probably the best file manager) http://www.7-zip.org/download.html
4. Drivers: http://d-h.st/a5kA
How to install drivers: Download and extract the above zip contents in a folder. Right click on My Computer > Manage > Device Manager. If your drivers are not installed correctly, it will show as unknown device in device manager. Right click unknown device > Click update driver software > Browse and select the extracted folder. If warning is shown, ignore it and proceed.
5. Patience and some brain xD :silly:
INSTALLATION:
Windows 7/8/8.1 is recommended
1. Extract the adb and fastboot tools in folder on your desktop named Redmi 2.
2.Download and extrack the fastboot ROM in the same folder too. Use 7zip software here to extract it.
3.Now move mouse to empty space in folder and while pressing shift, press right click. A menu will open. Select " open command prompt here" option. A command prompt window will open.
4.Power off your phone. Let it vibrate. Press and hold "Volume down and power" buttons until it enters fastboot mode.
5.Connect the phone to PC/Laptop in fastboot mode itself. Let the OS install drivers, make sure you have working internet connection.
6.Type the following command:
Code:
fastboot devices
Fastboot will return serial number of device(It can be any number don't worry if it looks weird). Click button below to see screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.If a blank space is returned, make sure drivers are installed correctly and phone is connected correctly.
8.If everything is okay, type the following commands one after another when previous process is complete.
I have shown a example for flashing recovery image below. Likewise you have to proceed for others.
Code:
1.fastboot flash boot boot.img
2.fastboot flash system system.img
3.fastboot flash userdata userdata.img
4.fastboot flash recovery recovery.img
5.fastboot flash cache cache.img
9.After this is completed, type the last command:
Code:
fastboot reboot
10.DONE.
Your phone will now boot in MIUI kitkat and you are ready to flash the official CM13!
Follow this guide for CM13:http://forum.xda-developers.com/redmi-2/how-to/rom-install-official-cyanogenmod-13-t3374589
HIT THANKS AND FEEL FREE TO ASK QUESTIONS HERE.
bootloader isn't locked, only partitions change bro
I flashed the images via fastboot and got bootloop...........
PROdelision said:
I flashed the images via fastboot and got bootloop...........
Click to expand...
Click to collapse
Device variant?
Did you try cm13? Try and tell.
Sent from my 2014818 using Tapatalk
is this how to the same with if i use MiFlash?
sennayan said:
is this how to the same with if i use MiFlash?
Click to expand...
Click to collapse
Yes. I'll try to update this with screenshots etc today.
Sent from my 2014818 using Tapatalk
Is this working with 2014813?
frosty234 said:
Is this working with 2014813?
Click to expand...
Click to collapse
It should.
Sent from my 2014818 using Tapatalk
noobpremium said:
It should.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
I made it with 2014813, and now I am stuck at boot with MI logo.
What can I do?
bisato said:
I made it with 2014813, and now I am stuck at boot with MI logo.
What can I do?
Click to expand...
Click to collapse
Flash twrp and go for cm13 :good:
Sent from my 2014818 using Tapatalk
I was now able to once Start after installing "your" twrp. I wiped data etc, but now it gives me error 7.
Edit: solved by once again flash twrp IMG through twrp itself. THX noobpremium
Device variant: 2014811, a.k.a. Wt88047, a.k.a. Redmi 2 WCDMA
I exactly followed your post and flashed the images via fastboot and got a bootloop.
Then used fastboot to install & boot a twrp-3.0.0-0-wt88047-20160309.img and proceed to install a cm-13.0 NIGHTLY-wt88047 ROM and, again, got a bootloop
plasticdoc said:
Device variant: 2014811, a.k.a. Wt88047, a.k.a. Redmi 2 WCDMA
I exactly followed your post and flashed the images via fastboot and got a bootloop.
Then used fastboot to install & boot a twrp-3.0.0-0-wt88047-20160309.img and proceed to install a cm-13.0 NIGHTLY-wt88047 ROM and, again, got a bootloop
Click to expand...
Click to collapse
Did you follow cm13 guide properly?
Did you wipe system partition
Sent from my 2014818 using Tapatalk
Hey so, I'm running HM2014811 redmi 2 on lollipop miui. I've followed your article, but when i try to flash system.img, fastboot comes up with an error (remoteata too large). So what should i do.
Luke T. Kirk said:
Hey so, I'm running HM2014811 redmi 2 on lollipop miui. I've followed your article, but when i try to flash system.img, fastboot comes up with an error (remoteata too large). So what should i do.
Click to expand...
Click to collapse
First erase data partition with this command:
Code:
fastboot erase userdata
And then flash userdata again
Edit: Maybe you'll need to erase system partition too and flash again.
Sent from my 2014818 using Tapatalk
noobpremium said:
First erase data partition with this command:
Code:
fastboot erase userdata
And then flash userdata again
Edit: Maybe you'll need to erase system partition too and flash again.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Nope, It's still saying 'remote: Data too large" on trying to flash either system.img or userdata on fastboot
Any other suggestions?
Luke T. Kirk said:
Nope, It's still saying 'remote: Data too large" on trying to flash either system.img or userdata on fastboot
Any other suggestions?
Click to expand...
Click to collapse
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
plasticdoc said:
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
Click to expand...
Click to collapse
Super thanks. I'll add it to OP for ubuntu guys. I have ubuntu too but i dont use it for flashing [emoji14]
Sent from my 2014818 using Tapatalk
plasticdoc said:
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
Click to expand...
Click to collapse
Thank you, i'll try it out. I should have included the fact that im running os x. So yes, i'll execute the flash all from terminal.
"flash_all.bat" will work alternative of typing commands manually? (2014818)