Database Develop

How-To: Fix Faulty Baseband and Faulty Modem

Fix Modem / Baseband JB AT&T ONLY... Sure did fix my problem!
Diagnosis for: (Random) no sound; no phone connectivity such as: WIFI; BLUETOOTH; GSM.
Can happen: Flashing wrong fw; Flash failure.
NOTE: Android SDK is required, go to your OS below and view "prerequisites" for more information...
Windows 7 method​Prerequisites: Android SDK - Tools and SDK! (install here.)
Instructions:
(1. Make a folder in the directory "C:/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "C:/qinara/" folder.
(4. Open a cmd prompt.
(5. Change Directory (CD) the cmd to your install location of Android SDK's Platform Tools (type it in to the command prompt.) to make
a command like the following example. Example: CD C:/users/YOUR-USERNAME/android/sdk/platform-tools
(6. Type the following command in...
Code:
fastboot flash modem C:/qinara/NON-HLOS.bin
(7. Wait for the modem to be sent and installed.
(8. Type the following command in...
Code:
fastboot reboot
(9. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(10. Open up your multi-tasking menu and open settings.
(11. Set "select network" to "automatic," then your done.
Ubuntu / Other Linux-distro method​Prerequisites: Android SDK - Tools only! (to install type the following cmds in terminal...)
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Instructions:
(1. Make a folder in the directory "/home/USERNAME/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "/home/USERNAME/qinara/" folder.
(4. Open a terminal.
(5. Type the following command in...
Code:
fastboot flash modem /home/USERNAME/qinara/NON-HLOS.bin
(6. Wait for the modem to be sent and installed.
(7. Type the following command in...
Code:
fastboot reboot
(8. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(9. Open up your multi-tasking menu and open settings.
(10. Set "select network" to "automatic," then your done.
Downloads​
-NON-HLOS.bin
Ask any questions below... :fingers-crossed:

Kinda feels that way...but on the Linux instructions just use ~/qinara/NON-HLOS.bin instead of /home/USERNAME/qinara/NON-HLOS.bin
~/ means the users home directory
Also, and I'm gonna add this to my faq, but download the fastboot I linked, rename to moto-fastboot, place it in ~/bin and add that to $PATH in ~/.bashrc (or where ever your preferred disto prefers it to be)
My actual path line in .bashrc (the part above I'm referring to is in bold)
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/share/android/bin:/share/android/adt/sdk/tools:/share/android/adt/eclipse:/share/android/adt/sdk/platform-tools:$HOME/bin:"
For the curious, I keep all my Android stuff on its own partition (/share/android) so all I have to do is add those directories to my $PATH if I decide to disto hop. If you dualboot, you can do the same thing only set the partition as NTFS or ext2 (there's an windows ext2 driver). I disto hop about once a month.

Don't have access to my desktop right now trying to install my new ssd and put Linux mint on it. (Noticed your a Linux guy, do you like mint?) Anyways I'll be sure to add that in later. Thanks.
Sent from my MB886 using xda premium

Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.

help...
can you tell me its working or not cause i have some gsm problem no signal due to band change

(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.430s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.720s
Oooooh Cool.....now after trying to find how to get out of the mess that created. I still dont have signal lol

i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???

yashrab said:
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
Click to expand...
Click to collapse
Yeah this method bricked my phone. I had to go back to stock through RSD, and lost root access. The good news is it was so easy to reacquire root thanks to Dan Rosenberg's programs.

Can I install stock though myth tool.. I think it does work just like RSD?.. Plz tell me cause I am totally noob in this part.. And I don't want to brick my phone..
Sent from my MB886 using xda premium

Moto Atrix work on any GSM carrier or.. ?
skeevydude said:
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
Click to expand...
Click to collapse
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?

lonesomedove said:
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
Click to expand...
Click to collapse
You should be able to, but I'll tell ya that some users have gone through multiple places to get it unlocked since not all the unlock services have the updated unlock codes we need.

Nope
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?

BackDoorNoBaby said:
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
Click to expand...
Click to collapse
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.

Thanks
skeevydude said:
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Click to expand...
Click to collapse
Got it. Thanks.
I'll check it out after my classes tonight and give an update.

Yup
Yup. That did it. Fixed the issue.
Back to my 4G!
Thanks again.

Anyone tried with CM10.2?

Nope. I know Cyanogenmod has issues at the moment, but I don't know if this will fix it.
Best I can say is to try it. Worst case: you reinstall the ROM. Or you can wait for a release version of CM 10 instead of a nightly.
I can say this didn't brick my phone, so you shouldn't have to worry about it. (but as always - no guarantee)
Sent from my Atrix HD using xda app-developers app

I really need help, I need something like this but for a company in Mexico. I tried this but it didn't worked.

Question if i reflash back to stock eith RSD LITE or myth tools will that fix my baseband i delete my baseband by accident
Dumb me

wcdma and lte network problem
i happen to own the mb886 the lte and wcdma used to work then i mistakenly went to change my base band to cellular (800-mhz) then the network went off so i changed it to (aus2 band (gsm-900/ dcs-1900/wcdma-850/wcdma-pcs-1900) but now am only able to get 2g or edge networks but am also in a 3g coverd area. can you guys please help me out

[Guide] How To Setup And Use Fastboot

Introduction:
I have found that many people are unaware how to use fastboot, which if you have ever owned an HTC phone or something from the Nexus line you know how important it can be.
About a year ago I got sick of answering questions about fastboot so I made a guide, but it was device specific. Not too bad but I was constantly giving the links to it for other phones... of course more questions just popped up.
So here i am making a comprehensive yet easy to follow (I hope) guide on how to set up and use fastboot. I will cover the basics for Windows and Liunx (sorry Apple users, just cant stand the product/company)
I plan to make a series of guides for XDA-University Thus far there is this guide and:
[Guide] How To Create Recovery Flashable .zips / update.zips
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
So where do i get fastboot? There are a few ways but most often I would recommend getting it from the Android SDK as it is will be up to date.
or you can use THIS HANDY TOOL created by @shimp208
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I will go over the Download and Installation Process in the Next Post
Then i will go over useful commands.
*Just a note, This guide is to always be considered under construction as I plan to continue to make additions such as more commands and pictures
I will continue to attempt to clarifiy when needed and add what I have missed. I have yet to drop any project or guide I have made on XDA and will help where I can
As always I encourage questions I may miss something or be vague, it is best to understand fully then not ask.

Setting up fastboot on Windows and Linux
What is Fastboot?
Fastboot is a protocol designed to flash signed/unsigned partitions to android phones directly into the phones flash memory. If you are familiar with ADB think of it in the same way.
If you're not, just understand it is a tool designed to help flash images such as recoveries, bootloaders, kernels, etc. to your android phone. For the most part you can not use much of fastboot unless you are rooted and have an engineering SPL (Hboot/Bootloader)
If using a Nexus device you in a sense have an engineering bootloader already so don't need to worry about it like HTC folks need. But Some Nexus lines will have different bootloaders with different capabilities.
This however is not a tutorial to root your phone so i will not explain this. I will though go over SOME basics as in unlocking your bootloader to allow it to be rooted.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How do I get fastboot for Windows?
Fastboot.exe can be downloaded to your computer from Google's SDK found
HERE download the proper package depending on what system you are using.
also
you will need the proper drivers to allow your PC and phone to communicate. You will find these in your devices specific forum or possibly you can use PdaNet
Okay i got it, whats next?
After you downloaded the SDK package to your PC see where it is located, somewhere like this for Windows
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
Of course put it where you like, just know where fastboot.exe lies
*If you want to skip the SDK, you can get ADB and Fastboot by themselves with THIS HANDY LITTLE TOOL created by shimp208
Note: After you have ADB and Fastboot you will may want to finish following this guide to add a path in environmental variables.
For Windows:
Although not necessary, but to make it easier i really suggest doing these steps:
left click the Windows (start) button > right click on computer > choose properties > go to advanced system settings > advanced tab > environmental variables > in the first box (user variables for _____) click new > name it
adb
Click to expand...
Click to collapse
> the value is the path from earlier
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
(yours may differ from this so double check it!) > in the second box (system variables) find a variable named
path
Click to expand...
Click to collapse
if one doesn't exist make one > double click on it > at the very end of the variable value add the same line as before but with a ; in front of it. like this:
;C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
alright click ok and you are done!
{
"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"
}
Why did I just do all that?
Well this allows you to open a command line from anywhere on your computer without changing directories to use fastboot. Pretty much we told your PC that when you type
fastboot
Click to expand...
Click to collapse
or
adb
Click to expand...
Click to collapse
into CMD where to find it. As you learn how useful fastboot and adb are this will help a lot as CDing to where you want to be is wasted time.
So I still don't know what to do or how to do it!
All right lets start simple, click the windows button and in the search field type
cmd
Click to expand...
Click to collapse
you will notice a window pop up that looks suspiciously like DOS. View attachment 1980110
Here you will see a blinking cursor after your directory, lets try this type
Code:
fastboot
a whole bunch of probably unfamiliar stuff should now pop up View attachment 1386065 (for the most part this is a list of commands that can be used in fastboot) if you get something like
fastboot is not recognized as internal or external command operable program or batch file
Click to expand...
Click to collapse
then we need to troubleshoot, but for now i will assume it worked.
Now try typing
Code:
fastboot devices
...and nothing will happen, Why? because there isn't a device attached. Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode. On many phones hold volume down while powering on, if this wont bring you to bootloader mode then see your device specific forum, if needed choose fastboot. Again try typing
Code:
fastboot devices
this time you should have a list of attached devices, this is displayed as the serial number to each. Being many commands will "do" things to your phone try typing
Code:
fastboot reboot
If your phone is now back and running your existing OS, congratulations! :good: You now at least have fastboot set up and working properly. Now lets try a few things out and see why this can be so helpful!
Click to expand...
Click to collapse
How do I get fastboot for Linux?
To get fastboot installed on your Linux box first download appropriate SDK package From Here
*Not all Linux distros are the same and I don't consider myself a Linux guru, I will explain what I know about the few distributions I've used but remember if something don't work look up specifics for yours HERE
After SDK is downloaded extract contents into home folder, maybe in a folder called Android, your choice.
Now we need to make sure we have the latest java JDK installed found HERE or if you prefer you can get it from the terminal
Code:
sudo apt-get update
sudo apt-get install openjdk-6-jdk
or if using Ubuntu, the software center. (I have heard people complain about JDK7 so to be safe stick with JDK 6 for now)
**I have a 64bit machine so I needed the 32bit libraries, you may not need this. If you do run this from terminal
Code:
sudo apt-get install ia32-libs
**As pointed out to me by trevd, if you are using Ubuntu 12.10 or newer you should simply open a terminal and run these two commands
Code:
sudo apt-get install android-tools-fastboot
and
Code:
sudo apt-get install android-tools-fastboot
If you never plan on developing for android or using other tools that come with the SDK
then this should be all you need. And you may also skip the JDK install. As most people will never attempt to create
an app or ROM or mod their phone in a way that they would need more than this, these simple commands should suffice.
Downloading Fastboot
ummm.. isn't that what I just did? Possibly, but as far as I know ADB, fastboot and everything else in platform-tools wont automatically download with the SDK.
Other have told me it does, so feel free to navigate to the platform-tools folder and see if you see these applications.
If you skipped installing the SDK and just installed fastboot and ADB from the command line you can skip down to creating a path. So if you got them, skip this, if you don't, do this:
From in a terminal type
Code:
cd ~/android-sdk-linux/tools
./android
**note depending on what you named the folder the downloaded and extracted SDK is in you may need to change your cd command to something else.
Now a new window will pop up, Click on "Available Packages" and you will be see two boxes. One is Android Repository and the other is Third-party Add-ons.
Click on "Android Repository" then click on Install Selected. now click on "Accept All" and then click on the Install button.
Personally I like downloading all that is possible here, you may have limited space or bandwidth so all you 'need' is the contents of platform-tools.
If you want to download some API's later go for it, they aren't needed unless you are developing.
Adding a Path
Just like in windows changing directories can be brutally annoying so lets add a path. Open a Terminal and type:
Code:
nano ~/.bashrc
or you can use gedit, whatever you have/like to use (sudo gedit ~/.bashrc)
At the end of this text (or at the begining add the following
Code:
Android tools
export PATH=~/android-sdk-linux/platform-tools:~/android-sdk-linux/tools:$PATH
**again be sure this is your path (neat trick, find fastboot from within platform-tools, right click on it, go to properties, highlight the location/path and copy/paste this)
Now click save, this will make so you no longer need to type ./adb all the time
I have been told a reboot is needed here but I don't think so, just type this into a command line:
Code:
source ~/.bashrc
Drivers? I don't need no stinking drivers!
True, sorta, but more than likely we will need to add the android rules so your device can communicate with PC. Open a Terminal and Type
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
now add the following lines:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_adb", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Depending on your device this should be all you need and then some, feel free to check out THIS for the most up to date vendor list.
View attachment 1980099
Now for a test!
So plug your phone into PC via usb, have it in fastboot mode (from within bootloader) and open a new terminal, type:
Code:
fastboot devices
If you see a string of #s and letters then success! :good: you are ready to learn the ins and outs of fastboot!
Click to expand...
Click to collapse

Using Fastboot To Unlock Your Bootloader
Do You need to unlock your bootloader?
For many phones this is necessary to root, for others it is a poor way to root your phone as you may not have full access.
Many HTC model phones can be rooted with various exploits, sometimes removing the radio secure flags completely.
If you have one of these devices than I recommend this, as true radio s-off is far superior to an unlocked bootloader.
But other phones, including the Nexus line, will be fine just unlocking and do not need to worry, Although some phones like the Nexus One can profit from a new bootloader altogether.
To begin the rooting process you simply need to unlock your bootloader with this command from a terminal/CMD
Code:
fastboot oem unlock
and the reverse of course is
Code:
fastboot oem lock
Be prepared for a full wipe of your phone when unlocking the bootloader!
But quickly if you have an HTC and choose to unlock your bootloader to root your phone follow these step:
Select your phone from the list HERE (you will need to create a log in)
there will be some legal mumbojumbo to click through (just saying you void your warranty but you knew this!)
you may need HTC sync found HERE as well as the proper RUU for your phone, the HTCDev site will inform you.
After which the site will move you through the steps to gain fastboot access, but if you followed my guide above just skip it all.
next you will need to get the identifier token, this is unique to your device and really just getting probably voids your warranty,
even if you stopped the guide here. to do so, open terminal/CMD and type
Code:
fastboot oem get_identifier_token
copy and paste this information into the prompt at the bottom of the page. Now wait for an email to get your token....
once you get the email with the token you can now follow their steps to unlock your bootloader...
really if at all possible i recommend not to do this method of rooting. But if you do, follow these same next steps that the Nexus devices will be doing...
Now that your bootloader is unlocked:
We will flash a custom recovery to your phone, then a custom already rooted ROM. To flash the recovery go to your device specific forum HERE and find the developers section.
Look for a custom recovery option and consider reading up on it there.
Different Android phones will have different custom recovery options depending on the developers for it. The most common is ClockworkMod, there are both touch and none touch recovery options.
some others are TWRP, 4EXT, AmonRa and Cannibal. Find out what your options are, pick one and download it.
If possible check the MD5Sum, Windows use: THIS and Linux use a terminal and type
Code:
md5sum <filename>
of course replace <filename> with the file name.
View attachment 1980095
If you prefer, GTK Hash is a nice program as well.
Now this should be an image not a zip, so if the extension is .img your good, if its in a .zip or .jar or whatever extract the image.
Take this image and (for simplistic sake) name it
recovery.img
Click to expand...
Click to collapse
**if using windows be sure to pay attention if your file extensions are hidden, don't name it recovery.img.img!
So be sure your phone is in fastboot mode and connected to PC, open a terminal/cmd in the same location that recovery.img is in
(cd to that directory or windows users can hold shift > right click in the folder it's in > choose open command here)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
**erase recovery is not necessary but i am OCD about wiping...
now if you get an okay! then your good :good:
Code:
sending 'recovery' (4930 KB)...
OKAY [ 0.521s]
writing 'recovery'...
OKAY [ 0.489s]
finished. total time: 1.10s
If not let me know what the output is and ill help you fix it. (I will also make a troubleshooting section in my final post)
Great! Now Let's Flash a ROM
In that same developers section for your phone, you should pick out a ROM of your licking. If possible i would suggest an older version of CyanogeMod as these builds tend to be quite stable.
Also some phones may have newer ROMs requiring you to do various things to your phone. Such as changing radios or bootloaders or other things we haven't gotten to yet.
So for now try to read the OP of the ROM you like and make sure you meet all requirements.
So Im not going deep into how to flash a ROM from recovery as this is not part of a fastboot guide.
But pretty much just pick a ROM and anything else you may need (gapps, kernel, etc) and put on root of SDcard (no other folder)
Then boot to recovery, wipe all you can (I'll teach you fastboot wiping soon!) and then flash ROM + whatever else you need to and then reboot.
Another Issue With HTC's Unlocked Bootloaders
Well if this not yet another reason to try to gain true radio s-off for your phone...
From with in that ROM that you flashed you also need to unzip and extract the kernel (boot.img) this will need to be flashed through fastboot.
Once all the above steps are completed reboot into fastboot mode, if your recovery doesn't have a quick way to do so just open a terminal/cmd and type:
Code:
adb reboot-bootloader
from here you will need to then open a terminal/cmd in the same location as that boot.img is and type:
Code:
fastboot flash boot boot.img
If it says okay you are finally done!!! Well done with flashing your first ROM but can you flash a ROM in fastboot? I mean do you need recovery at all?
There are ways, and ill teach ya in the next post!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Flashing a ROM through Fastboot
So Why Do I Need To Do This?
You don't, normally you would flash a ROM through recovery, but why not have another way? Maybe your recovery partition on your phone is corrupt?
Maybe you just want to say "I learned something new!" whatever your reason here are the simple steps:
To start:
We need to download the ROM of choice to your computer. Once complete find the folder that ROM is in and open terminal/cmd to that directory
(quickest way for windows; just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
*Its been a little while since i did this but the phone might automatically reboot after flash so no need to run the reboot command
As your phone boots into the new ROM, pat yourself on the back...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
A Note on Erasing/Formatting
You may have noticed earlier that I had you erase your recovery before flashing a new one,
now here I had you erase system and boot, you may be wondering why.
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
What about just flashing a single partition?
Sure this can be done, hell you can restore a nandroid if you want!
well first you need to make a nandroid back up (unfortunately fastboot cant make a nandroid for you :crying: ) Put it some where on your computer.
Personally I only keep maybe 2 or 3 nandroids on my phone's SD card as why waste space. I do however keep almost all my nandroids on my computer separated into different folders for different phones. So my path to a nandroid backup would be something like:
android/htcg2/nandroids/<nameofnandroid>
Click to expand...
Click to collapse
But here's the catch, most newer recoveries do tar backups I believe TWRP uses .win, these can not be flashed in their current form!
However most older recoveries use yaffs2 format for their backups, these will always work. Pretty much if you get a backup with various partitions as .img you're good to go!
**Hypothetically speaking here: you installed a new recovery and want to flash a nandroid made in old recovery but the two recoveries used different formats...
Well you can flash the images with fastboot, then make a new nandroid and you got them back!
...Maybe I'm stretching... oh well, here's how to!
Now the obvious stuff:
Have phone plugged into PC via USB and in fastboot mode, open terminal/cmd and change directories to that folder where your nandroid is in (or again just hold shift and right click > open command window here if using windows)
Now in terminal/cmd type:
Code:
fastboot devices
all is good when serial number is displayed, now type:
Code:
fastboot erase system -w
fastboot erase boot
*This isn't 100% necessary but I'm a firm believer in wiping before any flash, even a backup
Code:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
(of course change the image names if needed)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And you did it! :good: now you are almost a pro at using fastboot!
keep playing around, you'll get the hang of it and will quickly see that this is one of the best tools in the Android SDK.
It makes things much faster and easier and in many cases safer than the alternatives. Any questions... feel free to ask!
Happy Flashing!

What About Flashing Firmware?
Flashing any firmware to your phone can be dangerous but if possible the best and safest way is with fastboot.
Hypothetically you flash a new Hboot through recovery and this Hboot was corrupt in some way, if the flash takes you will have a bricked phone, hard bricked, only JTAG can bring it back.
But with fastboot you get to input your command to terminal/cmd an see the output, if something goes wrong, just DO NOT REBOOT until you fix the problem.
And again, checking MD5sums is nice when flashing software but a must when flashing firmware.
I will again recommend THIS for windows and using the terminal for Linux
Okay, Time To flash A New Bootloader!
Some phones will not allow bootloader flashes unless you remove the radio secure flags, if you have a phone like this check the developers thread for a how to.
To begin, find the appropriate bootloader (sometimes referred to as an Hboot or SPL) for your phone,
Now download and check MD5sum, have your phone in fastboot mode and open a terminal/cmd in the location your Hboot.img is stored.
Code:
fastboot devices
fastboot flash hboot hboot.img
and of course replace 'hboot.img' with whatever you titled your image
**Do not reboot if you see 'sending.... failed' need to see the 'okay!'
I am not trying to scare you as these instances are so rare, but knowing what to do ahead of time is just common sense.
Not all devices use the same terminology for partitions, so if the above does not work than consider changing to this command:
Code:
fastboot flash bootloader bootloader.img
Again replacing <bootloader.img> with the name of your image
Now flashing a new bootloader will more than likely repartition your phone, so from here you probably should flash a new recovery, then flash a new ROM.
Be prepared to do all this before flashing a new Hboot!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'm ready to flash a new radio!
Flashing a radio can also be dangerous, but again the safest way to do so is within fastboot. So if possible always flash radios in fastboot mode!
**I am not referring to the FM radio in your car, rather your cellular Radio, you know where you get reception... don't ask me how to add a FM radio to your phone!
Also know OEMs commonly use baseband and radio as interchangeable terms, for the most part this is the exact same thing
First things first, know why you are flashing a new Radio. Is it because you have poor reception? Poor data speeds? Poor battery life?
Yes a new radio can cure all this, but NO ONE can tell you which radio is best for your phone, not even someone living in the same city.
The best radio for my phone will not for sure be the best for yours, even if you live down the road from me. Don't ask what Radio is best! and only flash a radio meant for your device!
Now that that's out of the way, lets do the same steps as before:
Download appropriate radio
Extract if needed (should be in .img format)
For simplistic sake name it 'radio.img'
Plug in phone to PC and open a terminal/cmd in the same location as your radio.img
Code:
fastboot devices
fastboot flash radio radio.img
fastboot reboot-bootloader
Again only reboot if all goes well (It will if you follow all direction)
Upon rebooting your bootloader you will notice your radio version has changed, congrats! You're becoming a pro!
*note, occasionally OEMs package another image called rcdata.img along with a firmware release, if they do I also recommend to flash this along with the radio
Code:
fastboot flash rcdata rcdata.img
**another note, if possible try to match the ril libraries between your ROM and radio, this is device specific and you will need to see your developers thread for this info.
It is not always possible or necessary to do so, but many do say it help quite a lot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Flashing a Kernel
Earlier I went over flashing kernels as part of HTC Unlocked Bootloader Flashing, the process is the same for anyone else as well.
Locate the Kernel you want to flash
navigate to the folder it is in (should be in .img format and lets name it boot.img)
Code:
fastboot flash boot boot.img
But lets say you are a developer and have worked on a new kernel for your device, a quick and easy way to test it out may be to fastboot load the kernel:
Code:
fastboot erase boot
fastboot boot kernel ramdisk
As usual replace file/image names accordingly
If you do not want to erase the current kernel, just skip erasing.
But I would just have a working kernel.img handy and erase, this way I know there are no residual effects from previous kernel - choice is yours
Code:
fastboot flash:raw boot kernel ramdisk
fastboot reboot
Test it out and see how things go! Good luck! :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
As always, if you have questions or comments feel free to leave them here!
Happy Flashing!

What Are Some Other Things That Fastboot Can Do?
A Whole lot really... This guide would be forever long going through all of this. But I'm trying to progressively go through as many options as I can in order from simple to complicated.
I mainly am making this guide for beginners but I want the Advanced Android user to learn something too! Hope we can all learn from each other!
RUUs or HTC's ROM Utility Updates
This can be a way of returning to stock or updating to an official OEM update.
To do this make sure your bootloader is locked
(as far as I know RUU's fail if unlocked, but depending on phone engineering SPLs or having radio s-off can be safe - but not always so check device forum)
So boot into fastboot mode, open cmd/terminal in location of RUU then
If needed:
Code:
fastboot oem lock
then to get into RUU mode
Code:
fastboot oem rebootRUU
Then you will flash the zip, change command to correspond to proper name
Code:
fastboot flash zip rom.zip
If it gets stuck and you see a message like flush immediately! just do the above command again, often first try fails for some reason
Always know if you need to or should be flashing an RUU, some people do more damage to their phone just because they thought they were bricked and tried 'everything'
And if you're looking for OTA's (over the air updates) or RUU's for your phone HERE is a great source!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Some Useful Information About Your Phone
Lets say you want something basic like your device's model number, type:
Code:
fastboot getvar mid
the return output is your model number. Some phones are locked into only allowing new versions of an OS to be flashed, to check yours type:
Code:
fastboot getvar cid
cid: 11111111
Click to expand...
Click to collapse
If your return value looks like this then you have superCID, meaning you are allowed to flash older and newer versions of Android OS. And depending on phone you can just use this command:
Code:
fastboot oem changeCid
or possibly a common cid (SuperCID)
Code:
fastboot writecid 11111111
If you want to get a bunch of info quickly try this:
Code:
fastboot getvar all
Here you will receive an output of much of your devices specifics, such as bootloader and radio versions, devices name and if its locked, IMEI # and so on.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
What about trouble shooting?
There have been various devices over the years which have used inferior parts. like the HTC DZ/G2 or Glacier.
These phones, like some others, had two different emmc's installed; one worked great and one was prone to failure.
I found the easiest way to check which emmc was in the phone was with a few fastboot commands:
Code:
fastboot oem list_partition_emmc
fastboot oem check_emmc
fastboot oem check_emmc_mid
Of course this couldn't prevent a phone from the mysterious random hard brick, but it could tell you if your hardware was prone to failure or not.
There are also a serious of tests that can be performed depending on the bootloader you have installed:
Code:
fastboot oem list_partition all
fastboot oem partition_test all
Both of these commands you can substitute 'all' for 'system' 'cache' or whatever if you just need info or test a single partition.
You may have noticed that some of these commands require knowledge of hex editing, which of course no one is good at but the info is there if you want to search for it! So here is some more!
Code:
fastboot oem heaptable
fastboot oem imgcrc
The second command here will run a checksum for your hboot, recovery, boot, and system partitions.
I find it helpful to know the value of what the should be when phone is working good and can use this against another checksum if i have issues down the road.
System and boot will change of course, but recovery and hboot wont unless i flash a new recovery or bootloader, this can help check for bad blocks.
Speaking of bad blocks, lets look for some:
Code:
fastboot oem rbchk
Now having some bad blocks in your nand is not always going to cause your phone to be unusable, sometimes its a partition thing too.
Some of these commands don't do anything...
True, various devices and bootloaders will allow for various fastboot commands. two tests you can do to see what yours supports
fastboot
Click to expand...
Click to collapse
or
fastboot oem ?
Click to expand...
Click to collapse
typing just this into a terminal/cmd will give you an output of available commands for your device. I hope to add a bunch more soon but i need to finish my papers and studying for finals!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
A Bit More Helpful Tips For Booting
Sometimes you may have issues booting, earlier we went over booting a kernel you made yourself as well as flashing a kernel
What about just booting a kernel without flashing it to your device?
Code:
fastboot boot boot.img
The above, when executed properly, will boot a kernel from pc on your phone without flashing directly. There are times we need to force boot or just test.
What may be even handier is to boot a recovery without flashing it, this is done in the same manner as above and can let you use a recovery on your device without installing it.
Plug phone into PC, connect with USB cable and have phone in fastboot mode, now open CMD/Terminal in the same directory as your recovery image
Code:
fastboot boot recovery.img
Of course name image correctly to fit command or vise versa
Now you are in recovery of choice within your device without it being flashed to your recovery partition. There is a time and a place for everything, can you think of ways this may help you? Sure you can!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
as always... Happy Flashing!

Is There Anything Fun I can Do With Fastboot?
How would you like to go from this:
to this to this to this to this
Or really just about anything you want?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Of course I'm referring to the splash screen, the one that appears when you first boot your device, before the bootanimation.
This is a static image put there by the OEMs and often is real boring. True some phones have some neat ones, others little gifs, but really why not change it if we can?
Well in order to do this we need to know where our device in question stores the splash screen. If it has its own partition, your rooted, and your bootloader has fastboot capabilities we are good to go!
...well almost, remember when i talked about s-off earlier? This is low level firmware stuff, at least the way many device see it. Having root access doesn't mean we can do anything unfortunately.
I would suggest checking your phones forum to see if anyone know specifics to your device and where this partition is stored, if you need help other than from this guide feel free to post and ill see what i can do!
Ok, so I'll use HTC as an example here, we are rooted, we have an engineering bootloader, and security flags are removed. Now we need to find partition location.
Code:
mmcblk1p2 - "sd-ext"
mmcblk1p1 - "sdcard"
mmcblk0p31 - "misc"
mmcblk0p29 - "pdata"
mmcblk0p27 - "devlog"
mmcblk0p26 - "modem_st2"
mmcblk0p25 - "modem_st1"
mmcblk0p24 - "cache"
mmcblk0p23 - "userdata"
mmcblk0p22 - "system"
mmcblk0p21 - "recovery"
mmcblk0p20 - "boot"
mmcblk0p19 - "adsp"
mmcblk0p18 - "radio_config"
mmcblk0p17 - "radio"
mmcblk0p16 - "misc"
mmcblk0p14 - "splash1"
mmcblk0p12 - "bootloader" hboot
So this device keeps the splash screen in mmcblk0p14, this is very important to know and will change with most devices.
We will know extract original splash before we change it. Again I cant stress how important it is to know what you're doing when using dd commands!
So open a terminal/cmd
Code:
adb shell
su
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/splash.img
This will now pull the original splash and place it on your sd card named splash.img
***remember the above command differs for every phone!!
Now that we have this, keep a copy somewhere just in case.
You can now use a tool like FFmpeg to extract the image, use gimp to make a new one, and follow this simple guide if your confused. Or ask here and I can help.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You may have noticed none of the above used fastboot... huh, and here this is a fastboot guide!
Ok we'll just say you have a new splash image all ready and you want to flash it, but how? In the case of this phone fastboot is the way to go
Code:
fastboot flash splash1 splash.img
fastboot reboot
And done! :good: way to easy I know, put you're a pro at fastboot now so what did you expect!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And for future reference you can use dd commands to flash to your phone as well, but the don't call the "disk destroyers" for nothing!
Also its possible to flash in recovery, to the best of my knowledge I'm the only one to create flashable .zips for this (not bragging just saying I'd like to see more)
HERE Is an Aroma flashabe I made for the HTC Doubleshot
HERE Is an Aroma flashable I made for the HTC Vision
Both recovery flashable.zips allow the user to flash one of many custom splash screens and bootanimations with the easy UI Aroma brings
It is not as safe as fastboot, but I have never seen an issue when the code is done right.
I plan to make more for other phones as I have time, want one for your phone? Go through my scripts, feel free to copy and paste, I need no credit, just glad to see more people with more options!
If you need help making them, again just ask. I prefer in this thread over pm though as my inbox fills to quick...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Old stuff... in the process of editing to make things more clear....
Come one, like the previous stuff isn't fun!
Well many aren't aware that they can change the splash screen on their phone or tablet, this is just another partition most often like system, or cache.
Yes some phones will have it built into params or locked elsewhere in the firmware but often fastboot is a simple way of flashing a new splash screen.
To find out a list of your device's partitions i would advise to check you sites development thread here in XDA. But we can quickly do it as well with some simple ADB commands.
This guide does not go over ADB and for a better understanding search out one of many guides in XDA and elsewhere. (I am considering making one here as i have yet to see a comprehensive yet easy to follow guide)
Having said this, here are a few things you need to know. If you followed this guide and have fastboot working, ADB should also work just fine.
Know that fastboot is to be used in bootloader mode and ADB is used when booted into the OS or in most recoveries.
So now boot to your OS, make sure debugging is turned on, android 2.x and older this is found under settings>applications. 4.x and up it will be under developer options in settings.
Now connect your PC and phone via USB (wireless options are also a possibility here) You should notice a symbol in your status bar confirming debugging is on. (unless disabled) open a terminal/CMD and type:
Code:
adb devices
If you see your serial number lets proceed, if not post in this thread and i'll help.
Code:
adb shell
cat /proc/partitions
This will list all your partitions and their size, but this wont give you what each partition stores. There are different ways to do this for different devices, so you may need to try a few commands
Code:
ls -l /dev/block
ls -l /dev/block/platform/sdhci-tegra.3/by-name
the last command is for a device with a tegra 3 processor, of course will only work if yours has one (you may need to type 'su' to get commands to work)
you can also try:
Code:
df
busybox df -hm
Really all this isn't 100% necessary as someone probably found this out for you already. If not we just need to know the location and proper size of the image to flash.
I will help further if requested but as of know I'm going to assume we have this.
Alright lets flash the new splash screen already!
So we have a new image in .img format and it is the proper size. we will name it splash.img And as most phones that allow flashing a new splash we will call the partition its it splash1
**If your phone is different than whats listed here commands may very or not be allowed without changing bootloaders.
Back in fastboot mode, plug in phone... the usual
Code:
fastboot flash splash1 splash.img
fastboot reboot
Now that initial boot screen (before animation is replaced!) congrats!
**As you can see this section is poorly written, it is hard to universally apply a command to all phones as this command differs between them.
There are dd commands to flash just about anything, including splash screens, but dd commands can be dangerous and I would not recommend them to anyone who doesn't fully understand what they are doing.
Feel free to post with any questions!

Troubleshooting and FAQs
Some Common Questions and Answers
Q: When I open terminal/cmd and type fastboot devices i just get a blank line...
A: Well there are a number of reasons why this could happen, but here are the things you should check:
*Is the device powered on in fastboot mode?
*Is the USB cable in good shape (not a junky .99 cable)
*Do you have the proper drivers installed (Windows) Android Rules (Linux)?
*Do you have fastboot.exe on PC?
*Have you set up a path in environmental variables (Windows) or the path in .bashrc (Linux)?
****If not then what if you open the terminal/cmd in the location of adb/fastboot?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q: When I type in command fastboot <whatever command> I get < waiting for device >
A: Then you are either not in fastboot mode on phone, bad connection to PC, missing drivers (or android rules) - fastboot is installed and working just your devices isn't communicating
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q: When I type in command fastboot <whatever command> an error message like
Code:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
A: This means the fastboot command you are trying to use isn't supported by your current bootloader, to find the list of commands available to you type in one of these two commands:
Code:
fastboot
fastboot oem ?
Q: When I type in a command to flash <XXX> it starts to work but then I get this error:
FAILED (remote: Download size too large) finished. total time: 0.002s
A: Chances are this is not the proper image for your device or your are trying to flash to the wrong partition, double check that this is the correct .img (md5sums help)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q: When I tried to flash <XXX> I keep getting this error
Code:
sending 'recovery' (3518 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
A: This is because you don't have the proper permissions, you are trying to flash an unsigned image to a write protected partition. You will need to unlock bootloader or flash and engineering SPL, or find an OEM image.
This error is very device specific in the sense that I would need to know more about what you are trying to flash and what bootloader you have to answer properly
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q: When I tried to flash <XXX> or fastboot boot <XXX> I keep getting this error
Code:
downloading 'whatever here'....
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
A: This is often because of a few things:
first, make sure you have a high quality USB cable, and USB port is good. Just because the cable works for charging does not mean it is a good cable.
second way I've seen this issue, user is in bootloader mode but not fastboot mode. yes I often say this is one in the same, but double check, some devices specifically have a fastboot mode within bootloader!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*Note I have found many errors are due to not running fastboot with elevated privileges, try running fastboot as administrator (Windows) or su/sudo (Linux)
As people post errors or questions I will try to add more Q&As
Happy Flashing!

Nice Guide
Hi There
Nice guide there, good to see some of the more advanced stuff like booting over usb covered :good:
Couple of things
Fairly sure you don't need java or ia32-libs to run fastboot on linux but I suppose it doesn't hurt to install it . Also if you're running the last 2 version ubuntu , 12.10 or 13.04 ( or any ubuntu flavoured Linux ) then fastboot can be installed through apt.
Code:
sudo apt-get install android-tools-fastboot
adb is in there as well
Code:
sudo apt-get install android-tools-adb
EDIT: Also you don't have to do the erase command before doing the boot command as you can use it just to boot a kernel on it's own which would be very difficult if you just used erase to erase the ramdisk, the following are both valid
Code:
fastboot boot kernel
fastboot boot kernel ramdisk.img
Thanks

Thanks for the reply!
I'll be sure to add that in, I read a bit about this but I've just used old fashion install on all my Linux distros I've used. I'll be sure to add as many new Linux user choose ubuntu and apt get is just way easier.
I haven't had a chance to edit through everything yet, last day of finals were today and I needed some study breaks, hence a quickly written guide. I have lots more to add, and looking over some of my write up I'm far from clear on some pieces.
So yeah any input is much appreciated and I'll be cleaning this up soon!
Sent from my Nexus 7 using xda premium

thank you!
good man.

demkantor said:
what is fastboot?
Click to expand...
Click to collapse
can i use fastboot to flash firmware onto my phone and bypass getprop("ro.product.name") in the updater-script? or somehow flash an unsigned update.zip?
edit: thanks for this great guide, if you could just tell me which bits of the guide you think would be relevant to me that would be awesome. i just don't want to do something off my own bat and then it be absolutely redundant.

sure, fastboot should bypass the ro.product.name (but this is also easy to take out of the updater-script) and it allows to flash unsigned zips as well.
maybe explain to me in a little more detail what you want to accomplish and I could help you do it.
The reason i ask is that flashing firmware is very dangerous and flashing the wrong firmware can easily give you a brick. If all security flasgs are removed on your device you can flash whatever you want in fastboot (for the most part) but that wont mean you should. Let me know what it is you want to flash and hopefully i can tell you if it is safe to do or not.

demkantor said:
sure, fastboot should bypass the ro.product.name (but this is also easy to take out of the updater-script) and it allows to flash unsigned zips as well.
maybe explain to me in a little more detail what you want to accomplish and I could help you do it.
The reason i ask is that flashing firmware is very dangerous and flashing the wrong firmware can easily give you a brick. If all security flasgs are removed on your device you can flash whatever you want in fastboot (for the most part) but that wont mean you should. Let me know what it is you want to flash and hopefully i can tell you if it is safe to do or not.
Click to expand...
Click to collapse
I want to update my KIS LITE (v790 with 256mb ram) with a KIS LITE firmware from ZTE website. It's for a different country/telco, the product names match but the one in the update has productname_telco instead of the stock productname on my phone which i bought directly from china. I'm pretty sure it's all compatible, i have a rooted phone, and i changed the build.prop to match productname_telco but it still errors out updating in recovery at the product name check. (weird???) if i change the zip which is quite easy, it's unsigned and won't update. i'm trying to update specifically to "Greece KIS LITE SD card upgrading instruction & software package(Cosmote)-213550B0197ZTE Kis LiteV1.0.0B01\update.zip"

@knifey_au
ok so I downloaded and took a look at the file you want to flash
Code:
assert(getprop("ro.product.device") == "roamer2" ||
getprop("ro.build.product") == "roamer2");
assert(getprop("ro.product.name") == "P752D01_Cosmote_GR");
these are the three lines that need to be the same in build prop, but in truth if you havent a custom recovery than it may still see your product info in your recovery as you have the stock kernel=stock recovery
and these are all the lines in the new build.prop you are trying to flash
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRK39F
ro.build.display.id=ZTE Kis LiteV1.0.0B01
ro.build.version.incremental=20130427.041932.31486
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Sat Apr 27 04:30:41 CST 2013
ro.build.date.utc=1367008241
ro.build.type=user
ro.build.user=
ro.build.host=zte
ro.build.tags=release-keys
ro.product.model=ZTE Kis Lite
ro.product.brand=ZTE
ro.product.name=P752D01_Cosmote_GR
ro.product.device=roamer2
ro.product.board=roamer2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ZTE
ro.product.locale.language=el
ro.product.locale.region=GR
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=roamer2
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=P752D01_Cosmote_GR-user 2.3.6 GRK39F 20130427.041932.31486 release-keys
ro.build.fingerprint=ZTE/P752D01_Cosmote_GR/roamer2:2.3.6/GRK39F/20130427.041932.31486:user/release-keys
# end build properties
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.composition.7x27A.type=mdp
debug.composition.7x25A.type=mdp
dalvik.vm.heapsize=40m
#
# system props for the cne module
#
persist.cne.UseCne=none
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.fmc.mode=false
persist.cne.fmc.init.time.out=30
persist.cne.fmc.comm.time.out=130
persist.cne.fmc.retry=false
#
# system props for the MM modules
#
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
#
# system prop for opengles version
#
ro.opengles.version=131072
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
#
# system props for IMS module
#
persist.ims.regmanager.mode=0
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth FTP profile
#
ro.qualcomm.bluetooth.ftp=false
#
# system prop for Bluetooth SAP profile
#
ro.qualcomm.bluetooth.sap=false
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
#
#system property for Bluetooth discoverability timeout in seconds
#0: Always discoverable
debug.bt.discoverable_time=0
#
# System prop to enable/disable OMH. Enabled by default
#
persist.omh.enabled=1
#System prop to enable ehrpd capability
ro.config.ehrpd=true
# System property for cabl
ro.qualcomm.cabl=1
#
#System prop to determine availability of
#analog fm path
#
ro.fm.analogpath.supported=true
#
#System property for FM transmitter
#
ro.fm.transmitter=false
#
#System property for single instance recording
#
ro.fm.mulinst.recording.support=false
#
#System property for msm
#
ro.hw_plat=7x27a
#
#System property for Power Saving
#
persist.radio.add_power_save=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-zte
ro.com.google.clientidbase.am=android-tmobile-{country}
ro.com.google.clientidbase.ms=android-tmobile-{country}
ro.com.google.clientidbase.gmm=android-zte
ro.build.baseband_version=P752D01_Cosmote_GRB01
ro.build.sw_internal_version=COS_GR_P752D01V1.0.0B01
ro.build.baseband_version=P752D01_EUROPEB01
ro.build.sw_internal_version=P752D01_EUROPEV1.0.0B07
ro.build.baseband_version=P752D03B01
ro.build.software_version=GENERIC_P752D03V1.0.0B01
ro.build.sw_internal_version=GENERIC_P752D03V1.0.0B01
ro.camera.intrplt.2mpto3mp=true
ro.build.baseband_version=V766B01
ro.build.software_version=GB_P752A10V0.0.0B01
ro.build.sw_internal_version=GB_P752A10V0.0.0B01
ro.config.ringtone=COSMOTE_1_BACKRINGTONE_A_2.mp3
ro.config.notification_sound=F1_New_SMS.ogg
persist.sys.timezone=Europe/Athens
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r11
persist.sys.usb.enable_switch=1
persist.sys.usb.linux_switch=1
persist.sys.usb.switch_pid=0x1351
persist.sys.usb.linux_pid=0x1351
persist.sys.usb.default.pid=0x83
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-zte
ro.com.google.clientidbase.am=android-zte
ro.com.google.clientidbase.ms=android-zte
ro.com.google.clientidbase.gmm=android-zte
ro.camera.intrplt.2mpto3mp=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
not sure what your current android version is but this one is 2.3.6 and should be fairly easy to build a custom recovery for your phone allowing you to flash nonstock .zips
just follow clockwork or twrp guide on how to create your own
and there is no firmware in this package, just kernel, ROM, and recovery so it should be safe enough to flash as long as you have a backup of original.
best of luck!

i downloaded so many new updates trying to get one to flash that i actually forgot to check the version. i'm trying to upgrade from 2.3.6. now i feel dumb. i'll try and find the right update and actually check the version number this time. *facepalm. i'll get back to you.

knifey_au said:
i downloaded so many new updates trying to get one to flash that i actually forgot to check the version. i'm trying to upgrade from 2.3.6. now i feel dumb. i'll try and find the right update and actually check the version number this time. *facepalm. i'll get back to you.
Click to expand...
Click to collapse
how do i get to the version number in the update.zip? Never mind i got it.
All the KIS lite downloads from ZTE are 2.3.6. Which is a pitty, since the 512mb version of the v790 is supposed to have ICS and go a lot faster with it. nfi if ram is the only thing they changed though so i'm not going to try and install KIS firmware on KIS lite when I don't know if it will bork things up. Unless you want to look at the phillipenes download for the v790 from ZTE website and tell me if you think it will work for the kis lite.

Hate to say it but it will doubtfully work without a lot of modifications, as handy as fastboot is it won't help with this.
Unfortunately if your phone doesn't have any custom ICS ROMs your best bet in getting one is to create a devices tree and then make it yourself. Simply flashing it from another device will probably leave you in a boot loop at the least and possibly a brick
Sent from my Nexus 4 using xda premium

Would you mind if I linked this thread in my signature?

russellvone said:
Would you mind if I linked this thread in my signature?
Click to expand...
Click to collapse
Of course not! Feel free to share this thread with whomever you choose, my goal is to help anyone and everyone. Now if I could just finish adding all I plan to...
Sent from my Nexus 4 using xda premium

[Q] ??? OMAP4440 refreshing every second as I connect KFHD 7

My kindle got screwed up again after a restore from back up. Now it goes like this
a)shows Kindle fire (yellow) 1 second
b)shows fastboot 1 second
c)then screen goes blank, until I switch it off
As I switch it on, repeats a, b & c
The device manger keeps searching & refreshing OMAP4440 drivers every 2 second( with ding sounds)
This happens both with a factory cable as well as the standard usb.
Any one knows how to troubleshoot this?

Bump

OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

looks like your device doesn't have enough power to stay in fastboot. just leave it charging for about an hour even if it doesn't display anything. it should still be charging.

UMM!!
stunts513 said:
OK I have no experience with bricked kindles that are bricked in that manner but I think kindle fire first aid may be useful, but if that device is not installing fast enough because of it shutting off before windows can complete installing the drivers I have to say and this may not be useful or something you want to try, but Linux might be the way to go, it typicly doesn't need to install the driver because drivers are either integrated into the kernel or loaded immediately as modules, and Linux comes with quite a few drivers by default. So your device would be recognized as its flashing off and on, from their I don't know what you could really do even if u have access to fast boot if it keeps shutting off evert two seconds I don't see you successfully flashing it unless u know how to write a bash script that waits for it to show up and then immediately flashes the boot loader, which is fairly small, it might be able to flash before it shuts off if your extremely lucky. From what my thought track is seeing i think it might stop with the constant rebooting once you manage to flash the bootloader, from their i woukd see fixing any other bad partitions as easy. This is all from a novice unbrickers standpoint. I may be completely off, haven't ever used kf first aid, so I don't know if your brick is fixable or not. Just thought I'd post my two cents since no one has been posting any help for you yet. Hopefully someone else that knows more about this can help you out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
1. I tried pluging it in ubuntu-12.04-desktop-i386 live usb, didnt detect the device. Do I have to download some thing before?
2. After a,b,c, the screen goes black but the OMAP4440 keeps refreshing in device manger it only stops when I push the power button for more than 20 seconds. I beleive the KFHD is not switching of but just goes to a black screen.
3. What is a bash script?

OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Hey, the description is quite technical for me. Can you write a step by step guide, starting from once i boot up a linus live usb (12.4 ubuntu)?
stunts513 said:
OK bash is a way more flexible scripting language you use in Linux. Think the Linux equivalent of a windows batch file but way better. You said it was going into fast boot for a brief moment. Before rebooting, I figured if its long enough for the fast boot command to recognize it in Linux, you could have the command for flashing the boot partition handy in a terminal. I figured if you had a stroke of luck, because the boot partition is so small, you might be able to flash it and unbrick it to at least get it to boot into fast boot to the point where you could restore the other partitions. I don't remember how exactly the fast boot command works in terms of waiting for the device to show up, that's why j was thinking use a batch script to repeat itself until sometching happened, but if it waits for the device u could simply run fastboot -i 0x1949 flash boot boot.img. Note boot.Img would be whatever the boot image restore file is called. Also Ubuntu probably is detect it, you must don't know it, its not going to popup anything or do anything unusual when its detected, only way u would know is to either install a device manager, I use a gnome one because I use an older distro of ubuntu, or run a command from a terminal the moment u see fast boot screen, I don't remember the command offhand, actually running dmesg would probably show it being picked up as a device connected, not sure what exactly it would say though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

I am literally falling asleep right now, I will write it tomorrow after I finish writing my résumé... I will warn you it will be slightly vague because I don't use the newer distributions of Ubuntu and am unfamiliar with the ui. Actually for simplicity I will upload a zip file with the fastboot binary and any files it requires, so I don't have to explain how to install stuff in Ubuntu. Hopefully the nautilus browser is the same. For the record nautilus is basically like Ubuntu version of windows explorer. As long as you can find your home folder and launch a terminal you should be able to follow my vague instructions. Anyways I will write a guide tomorrow since I am literally nodding off.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.

Your problem is that you are using OMAP drivers instead of fast boot or adb drivers.
Sent from my Amazon Kindle Fire HD using xda app-developers app

It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
It does that yes, but only after it stays in fast boot for a few seconds, so we are trying to catch the kindle while its in fastboot with Linux so it can try to reflash the boot loader, if we could succeed in that then getting the rest working would be the easy part, though this as is is very difficult, only reason I even suggested trying this is because the boot loader is so small it doesn't take that long to flash, so I am hoping for it to flash in the few seconds it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
If the device IS actually going into fastboot, then it's entirely possible to re-flash the bootloader.
In order to do this, you have to enter the command while the device is unplugged, then plug it in when you see "waiting for device". As soon as fastboot mode is detected, the command will execute and the bootloader will be flashed, but be warned....
While flashing the bootloader happens rather quickly, if for some reason only part of the bootloader is flashed, the device will likely be unrecoverable. I suggest that you make sure the md5sum of the downloaded u-boot-bin checks out, and that you aren't using an extraordinarily slow computer.

Yea at this point his kindle is going to go either way, either way though if he didn't try what he's doing or if he did and it didn't work he'd be sending it into amazon though more than likely and seeing if they'd take it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
I lost you on step 5. Which website? the md5sum that i get is (bb029673d8f186db4dff6d38f4aa28cf) <---Nevermind. I know what website you are talking about.
---------- Post added at 01:49 AM ---------- Previous post was at 01:22 AM ----------
Once I get to number 6 I get this?
[email protected]:~/Kindlefix$ ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
bash: ./fastboot: No such file or directory
And the fastboot file and kfhd7...bin file are inside the folder.

Update.. FIXED
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!

lo pudiste solucionar?
ToPViP said:
Thanks @stunts513 for your help. I was able to fix my kindle. The linux didn't work. Somehow it managed to stay on fastboot screen. I went back to Windows. Opened a command prompt typed fastboot -1 0x1949 getvar product and hit enter. it waited for device. turned Kindle off. plugged fastboot cable to kindle then PC and was able to read it. Once that happened I was able to manually input the info
{fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
fastboot -i 0x1949 flash recovery "C:\KFFirstAide\path\to\recovery.img"
fastboot -i 0x1949 flash system "C:\KFFirstAides\path\to\ystem.img"} ofcourse changing the paths.
I downloaded Hashcode's Kindle OS from here http://forum.xda-developers.com/showthread.php?t=2218475.
And it worked.
[ Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Orlando>fastboot -i 0x1949 getvar product
< waiting for device >
product: Tate-PVT-08
finished. total time: 0.004s
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\path\to\boot.img"
target reported max download size of 1006632960 bytes
error: cannot load 'C:\KFFirstAide\path\to\boot.img': No error
C:\Users\Orlando>fastboot -i 0x1949 flash boot "C:\KFFirstAide\images\boot.img"
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 2.826s]
writing 'boot'...
OKAY [ 0.688s]
finished. total time: 3.517s
C:\Users\Orlando>fastboot -i 0x1949 flash recovery "C:\KFFirstAide\images\recove
ry.img"
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 2.826s]
writing 'recovery'...
OKAY [ 0.681s]
finished. total time: 3.513s
C:\Users\Orlando>fastboot -i 0x1949 flash system "C:\KFFirstAide\images\system.i
mg"
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [312.188s]
writing 'system'...
OKAY [ 73.516s]
finished. total time: 385.710s]
THANKS to all the 50+ threads that I read about this. And all the people that make it happen!
Click to expand...
Click to collapse
hola soy latino pero frecuento bastante el foro, antes no opinaba puesto que no hablo ingles , alguno que hable español me podria ayudar? me pasa lo mismo que el joven que inicio el tema, veo que algo hizo para arreglarlo pero yo no entiendo , porfavor ayudenme:crying:

stunts513 said:
OK I haven't finished my resume but I figured this wouldn't take long to explain and I will just keep procrastinating if I don't clear everything in my mind. OK so to start with you need to open a terminal, I am unfamiliar with exactly where that will be located on new versions version f Linux because it doesn't use gnome ui. Last I checked if u hit the Ubuntu logo a menu with apps would come out, if there's an accessories section it would probably be there, if not there's a search function, if not that try Ctrl alt t, not sure if that keyboard shortcut is standard or not though.OK now I feel I can use numbers.
1. Download included zip file( will post from my PC in a moment)
2. Open the home folder in Ubuntu, again unsure where this will be but usually it shows u some things on that bar on the left, if home isn't mong them then click on like videos or music and go up a level, that is usually home.
3. Extract the contents of the zip file to a folder in the home directory, let's call the folder kindlefix
4. Download http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin this file and put it in the kindlefix directory.
5. In the terminal and type "CD kindlefix", now type "md5sum kfhd7-u-boot-prod-7.2.3.bin". Now check that the string outputted is the same as the one on the website. If it is continue to next step if not try redownloading the file again and checking it again.
6. In the terminal now type ./fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
7. Try hitting enter with your device powered off and when fastboot says waiting for device, power it on with fastboot cable.
Like I've been saying this is going to take a bit of luck to flash successfully, and if it does try to flash and fail it will probably just brick it worse, at which point I'd return to amazon. You might have to repeat this step a few times to get the timing right to see if it will flash, its a fairly small file so u might get extremely lucky. Post back and tell me what kind of luck u manage to get.
Click to expand...
Click to collapse
Lol,nice guide mate. I saw the title and just thought,"How the hell does OMAP4 refresh itself?" Anyway,I think that he would be better off installing android-tools-fastboot since he's running Ubuntu.

Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.

stunts513 said:
Yea true, I hadn't familiarized myself at the time with the package names and such, just checked that post and man is the date old, almost a year... Learned quite a bit since then.
Click to expand...
Click to collapse
help me please please

Translation: hi i am latino but quite frequent the forum, not previously thought since I do not speak English , some speak Spanish could help me ? I feel the same as the young man who started the topic , see something done to fix it but I do not understand , please help : crying :
My Spanish is horrible so I ran it through Google.
If it is doing exactly what the original poster is doing rather than showing up only as a omap4boot and not turning on then I recommend using Linux and running "fastboot -i 0x1949 erase boot" once it clears the boot partition it should kick it into fastboot until the boot partition gets re-flashed.

[GUIDE] How to revert back to Android Wear 1.5

How to revert back to Android Wear 1.5
Flashing stock AW1.5 build:
- Unlock your bootloader
- Reboot into FASTBOOT MODE
- Download STOCK ROM MWG68 images
- via adb type commands:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot reboot
How to block OTA to AW 2.0
- adb shell
- pm disable com.google.android.gms/.update.SystemUpdateService
- pm disable com.google.android.gsf/.update.SystemUpdateService
- exit

ingbrzy said:
How to block OTA to AW 2.0
- adb reboot bootloader
- adb shell
- pm disable com.google.android.gms/.update.SystemUpdateService
- pm disable com.google.android.gsf/.update.SystemUpdateService
- exit
Click to expand...
Click to collapse
This probably won't work, you don't have adb shell available in bootloader, and while booted up you can't use the pm disable command without root..

Maxr1998 said:
This probably won't work, you don't have adb shell available in bootloader, and while booted up you can't use the pm disable command without root..
Click to expand...
Click to collapse
true.. it will be more easier to boot TWRP, disable dm-verify and edit build.prop line
Code:
ro.build.id=MWG68
to
Code:
ro.build.id=MWG68_something

Thanks, i had to revert because i started getting random reboots since 2.0... Now I'mm gonna wait and see if it continues.
BTW, i think you forgot "fastboot oem lock" after downgrading.

after following the guide and flashing aw 1.5 I get an error saying zenwatch manager has stopped and then the reboots, and so on.
any ideas what went wrong and how can I fix this?

asafgolan said:
after following the guide and flashing aw 1.5 I get an error saying zenwatch manager has stopped and then the reboots, and so on.
any ideas what went wrong and how can I fix this?
Click to expand...
Click to collapse
make factory reset.. unpair and reset in the settings..

ingbrzy said:
make factory reset.. unpair and reset in the settings..
Click to expand...
Click to collapse
Thanks, that did the trick!

I'm having to much issues with 2.0 and overall I hate the update, so this guide is very appreciated, yet my watch is brand new and I don't want to mess things up, can you please do a complete guide with links to all the software needed and stuff? This seems to be for those who are already in the "knowing how to flash the FW", I believe I need to unlock the bootloader to in order to revert to AW 1.5 right? Or isn't that needed?
Thanks for the help @ingbrzy

Any chance one of you can help with this issue?
https://forum.xda-developers.com/zenwatch-3/how-to/fastboot-recovery-getting-g-co-abh-t3637403

Ok, I've been doing some reading and I'm almost ready to flash the watch back to 1.5, but just in case I'll make here the full list of what I've done/about to do, please check if all is correct:
1 - Download and place the Platform-tools folder from here on a easy access place to access on your PC
1.b - Edith Path Variable as shown here just be make things easier
2 - Enable USB debugging on watch by going to the watch Settings/System/About and pressing a few times on the Build Number
2.B - To check if the connection is well done between watch and PC open a command line on Windows and write "adb devices", it should show the watch SN listed
3 - Unlock the bootloader!
3.1 - Reboot to fastload (via *adb command* (You do this by opening a command prompt window from within windows itself) "adb reboot bootloader")
3.2 - type command "fastboot oem unlock"
4 - Download STOCK ROM MWG68 images
From here is where I have doubts, DON'T FOLLOW THESE INSTRUCTIONS until someone more experienced confirms if it's correct or not
5 - Place the files unziped: system.img / boot.img and recovery.img downloaded on point 4 inside the platform-tools folder in point 1
6 - Open a command prompt window and past the following code ***DOUBT*** Full code at once as shown bellow or line by line followed by enter??
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot reboot
7 - make factory reset on watch by... "unpair and reset" in the watch settings...
7.1 - Re-lock bootloader is advised? How and why to do it?
8 - Don't install AW 2.0 again?
@ingbrzy is this correct or am I missing something?

Thank you for this thread :good:
I'm back on 1.5 it's better for me in this moment...
My watch understand me again :laugh::laugh::laugh:
Edit:
I have two questions:
How I lock bootloader?
How to block Ota? Easiest way?
Thank you very much

Android Wear Updates
Does anyone know if leaving the bootloader unlocked prevents android wear 2.0 OTA
updates or any other updates?
Thanks, have a great day!

Misterjunky said:
Does anyone know if leaving the bootloader unlocked prevents android wear 2.0 OTA
updates or any other updates?
Thanks, have a great day!
Click to expand...
Click to collapse
No, I have unlocked bootloader and after night my watch download AW2.0 update

TWRP Recovery
I wonder if installing TWRP recovery might prevent Android Wear 2.0 OTA update?
I am on Android Wear 1.5 and do not want to update or get notifications to update.
Thanks,
---------- Post added at 01:02 AM ---------- Previous post was at 12:47 AM ----------
Hoffmanns said:
No, I have unlocked bootloader and after night my watch download AW2.0 update
Click to expand...
Click to collapse
Have you or anyone found a way to delete the AW2.0 update file from the watch?
Thanks!

Misterjunky said:
Have you or anyone found a way to delete the AW2.0 update file from the watch?
Thanks!
Click to expand...
Click to collapse
In this moment NO
Factory reset in recovery may help...
But I need block OTA update first

re: Build Prop file
ingbrzy said:
true.. it will be more easier to boot TWRP, disable dm-verify and edit build.prop line
Code:
ro.build.id=MWG68
to
Code:
ro.build.id=MWG68_something
Click to expand...
Click to collapse
@ingbrzy
Is it possible to use adb to pull and push the build-prop
file from /system to /sdcard or some other place where it would be
accessible making it easy to edit without rooting the watch?
(preferably someplace in Windows 10 or in my S7 Edge phone?)
If it's possible, could you please post the adb commands to pull and push the file?
Thanks in advance, have a great day!

I may go back as well. Aw 2.0 hasn't been a totally smooth experience even after wiping data and clearing cache. Sometimes it'll stutter and I will end up clearing all notifications instead of going one by one

Someone, please explain how to block OTA update to 2.0.... Please

re: Block OTA notifications
avchd said:
Someone, please explain how to block OTA update to 2.0.... Please
Click to expand...
Click to collapse
The only way I found to block updates and notifications for updates
is to ROOT the watch.
I rooted my watch 3 days ago after really trying to like this AW 2.0
but after all was said and done I just could not see any reason to
keep the new AW 2.0.
The only two things which we good and nice in AW 2.0 was the
really good looking and smooth/fast scrolling of the app drawer
and the nicer notifications which AW 2.0 has.
But everything else in AW 2.0 is really crappy way too crappy for me.
If you are interested in rooting and twrping your watch here is the link
with step by step instructions and download links for the rom.
Android Wear v1.5 pre-rooted and twrp'ed custom rom:
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340
The main problem with keeping AW 1.5 without flashing
a custom rom is all those OTA notifications you get over
and over again without a way to disable the notifications.
Come on guys, do we really need a Google Play store in our watch... LOL
Also the only way a watch can be called "stand-alone" is if it has a sim card.
Good luck, have a great day!

Even though I knew what I was doing, I was on a new computer so I "followed" your instructions because I've never seen anyone write it out so thoroughly from no ADB at all, and glad to say you pretty much nailed it through that. Except step 2, it's more like a whole bunch of times. Don't know why you've gone un-thanked and un-replied!
Step 5 is unnecessary because of the method of setting up ADB with the path variable described in 1b (if you don't do step 1b, then the files need to be in the platform-tools folder). You just need to get to the same folder in the command prompt as the files. The command prompt by default opens to C:\Users\pyroguysf (or whatever your own name is), which is where your downloads folder is located by default, so if you unzip the files to your downloads folder, type "cd Downloads" to navigate into your downloads folder. Once you're in the same folder as the img files you unzipped, then run the commands listed in step 6, each line, one at a time. After each one, it should show the progress, and make sure it says completed not failed (I forget the exact words used) before going to the next. If it fails that's a separate topic, but it shouldn't. I always advise a factory reset after any significant software changes. Re-locking the bootloader is for security's sake, and while not 100% necessary, is highly recommended, unless you plan to be changing the software again anytime soon (I see a modified version in this thread that supposedly has OTA's disabled I might try, but this is slightly more advanced). Re-locking is basically the reverse of step 3 - reboot into bootloader with "adb reboot bootloader" and then once it's there "fastboot oem lock" instead of unlock.
Edit: That's right, you get the message upon boot for a while that your device can't be checked for corruption when it's unlocked. Also, my watch won't boot now, so I'm going to try a few more things... That's why I waited until the weekend.
Edit2: Re-unzipped the files (md5 was fine), did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata" in step 6.
Edit3: Edited the quote from MK2ever below with what worked for me.
MK24ever said:
Ok, I've been doing some reading and I'm almost ready to flash the watch back to 1.5, but just in case I'll make here the full list of what I've done/about to do, please check if all is correct:
1 - Download and place the Platform-tools folder from here on a easy access place to access on your PC
1.b - Edit Path Variable as shown here just be make things easier
2 - Enable USB debugging on watch by going to the watch Settings/System/About and pressing repeatedly on the Build Number until it says "you are a developer!"
2A. Go to Settings>Developer Options and turn on "ADB Debugging" and plug your watch cradle into your computer and wait until windows installs drivers (Win 7 found them automatically for me)
2.B - To check if the connection is well done between watch and PC open a command line on Windows and write "adb devices", it should show the watch SN listed
2.C - when your watch asks to allow connections, tap "always allow from this computer"
3 - Unlock the bootloader!
3.1 - Reboot to fastboot (via *adb command* (You do this by opening a command prompt window from within windows itself) "adb reboot bootloader")
3.2 - wait until the watch says "fastboot mode" then type command "fastboot oem unlock"
4 - Download STOCK ROM MWG68 images
5 - Place the unzipped files system.img boot.img and recovery.img into your downloads folder.
6 - Open a command prompt window and type "cd Downloads" to get to navigate into your downloads folder (Windows 7 default, 8 and 10 too I think) and then enter the following commands one at a time waiting for it to give a "completed" message before moving on
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
7 - make factory reset on watch by... "unpair and reset" in the watch settings...
7.1 - Re-lock bootloader is advised. Repeat steps 2 through 3.1 and then "fastboot oem lock"
8 - Don't install AW 2.0 again?
Click to expand...
Click to collapse

unknkown oem command

Hey folks, long time xda user heavy search user results in minimal posts..
ok here we go.
I unlocked bootloader and rooted device with magisk now im attempting to re lock my boot loader.
i factory reset device and flashed google factory image with supplied zip file from google
command im using is
"fastboot oem lock"
results
C:\Users\RyeMc>fastboot oem lock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed
this is first lines from google factory image...
Sending 'bootloader' (8761 KB) OKAY [ 0.253s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
next i opened cmd and entered
"fastboot flash boot" then went and moved boot file into cmd window and said successful also tried boot_a and boot_b
unsure why i have tried to re download sdk manager android studio and input the file locations in the path under advanced settings.
albeit iv been out of the root game for a couple years made the mistake of getting a note 8 so i was stuck in that eco system.
some help or advice would be nice thanks.
before i rooted i made sure i was able to lock and unlock bootloader .

Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk

Thaiban said:
Use Adb tools or Sdk tools to unlock your phone.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
device is currently unlocked looking to relock device..

the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.

uicnren said:
the correct command is: fastboot flashing lock
make 100% certain however that your device is 100% stock before relocking, very good chance of bricking it if it is not.
Click to expand...
Click to collapse
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.

RyeMcFly17 said:
C:\Users\RyeMc>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
im going to go double check my path make sure it still exist. i did try and download sdk tools again.
Click to expand...
Click to collapse
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.

uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
What he said! :laugh:
Easier Windows choice : r29.0.6

download the latest platform tools and extract it, in the folder with the PT files in the top search bar type cmd and then try.

oem unlocking already unlocked
uicnren said:
if you want an easy (does require a little work on Windows) fool-proof way to keep adb/fastboot up to date and installed correctly, see: https://github.com/corbindavenport/nexus-tools
Easier Windows choice: https://developer.android.com/studio/releases/platform-tools.html
No need for the SDK or anything else, unless you actually dev apps.
Click to expand...
Click to collapse
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.

RyeMcFly17 said:
resolved added sdk platform tools to path in advanced settings flashed new google image and retired fastboot flashing lock and seems to have worked, thanks for all your paitence and advice. ill head back to the shadows and read read read before i post again till next time folks.
Click to expand...
Click to collapse
:good::good:
glad you got it sorted.