Database Users

Baseband

I'm about at my wits end trying to figure out this problem of mine.
Here's a quick overview of my situation, so I don't have to go through it again:
http://forum.xda-developers.com/showthread.php?t=1301091
Anyways, I decided to take another shot late at night to see if I could get this working. I'm running on 3.2.2 right now, build HLK75D, with no 3G/4G connectivity. I looked at a screen shot of a stock updated 4G Xoom's settings and I noticed that my baseband is the only thing different.
Is there some way to change the baseband from what it is now (CDMA_N_03.1A.54P) to "CDMA_N_03.1A.52P ltedc_u_05.15.00"?

I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.

Jewremy said:
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Click to expand...
Click to collapse
Yeah, well, I don't have either 3G or 4G. My Xoom says activation successful over Wi-Fi, and I have full signal with the Verizon towers, but it just doesn't connect.
I still haven't heard anything back from Motorola regarding any way to get the baseband back to the LTE version.

Guys use Motorola stock imgs, but remove your sim card after you flash it. See if it connects to 3g then. If not look for the hlk75c stock root on here flash that with your sim in.
Sent from my Xoom using xda premium

HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium

hammer4203 said:
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.

Did you flash hri66? What kernels have you tried? Oh and are you in a 4g area, cuz that can cause an issue if your not.
Sent from my Xoom using xda premium

http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium

hammer4203 said:
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I've tried AceXMachine's solution. Still no deal.
No matter what image I've used, I still have no option for LTE in my mobile network settings. My baseband still has never changed back to LTE.
I live in the dead center of a strong 4G area. My 4G was working fine prior to making the stupid mistake of flashing over what Motorola sent back.
Jewremy said:
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Click to expand...
Click to collapse
And that is exactly what mine says when I power up BP.
I just received a total generic e-mail response from Motorola telling me to make sure to check for updates, etc.
I replied to them and told them that my baseband is the wrong version and that my LTE radio is turned off. Lets see if they can provide anything to help out.

Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium

hammer4203 said:
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/

dethrok said:
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Click to expand...
Click to collapse
No. This is lower-level software. It's part of the bootloader, governs the radio. The build.prop files are the same between 3.2.2 back from moto and 3.2.2 upgraded from stock.

I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium

I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.

hammer4203 said:
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. EDIT: Nevermind. Don't bother.
zarkuu said:
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
Click to expand...
Click to collapse
See above in this same post.

Well, this is all hurting my head. Motorola e-mailed me back and said they were bumping my case up to their repair escalation team and I'll be getting a call in 1-2 days.
Hopefully they'll still help me out when it was my own stupid fault that I screwed up my connection. Maybe they'll be able to give me a solution to turn the radio back on.

Jewremy said:
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. I'm thinking the baseband is contained in the ebb partition, also known as the bootloader. Reflashing the bootloader is extremely risky. You really don't want to do that. It's at /dev/block/mmcblk1p1. Controls the whole boot sequence. The HTJ85B update overwrites/updates the bootloader, which is what could cause our issue.
Click to expand...
Click to collapse
OK, this makes sense to me since I have flashed back to HRI66 and did OTA updates to HTL85B and nothing else would presumably have changed it back. My mistake was probably allowing the device to boot under HTJ85B. If I had just done it through recovery and then flashed back to HLK75C it wouldn't have touched the bootloader. I bet some people didn't do that and so they work when flashing various restores. I understand it is risky to flash the bootloader (because if it goes wrong you won't be able to even go to fastboot) but what other option is there other than RMA back to Moto? Do we think Moto will be releasing stock images for this new bootloader anytime soon? That's really more of a rhetorical question I think.
I guess if someone wants to try making a backup I might try flashing it.
From http://forum.xda-developers.com/showthread.php?t=1294824
Pulling your own images
1. Flash a custom recovery
2. Boot straight into recovery.
Code:
adb shell
mount /data
mkdir -p /data/media/images
dd if=/dev/block/platform/sdhci-tegra.3/by-name/ebb of=/data/media/images/bootloader322.img
sync
Then reboot back into android and pull it off your device.

See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium

I'm in the same boat: http://forum.xda-developers.com/showthread.php?t=1299485
Hopefully we'll find an answer soon.

hammer4203 said:
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
No dice. I've checked all the OTA updates I know about:
19dea2ba1ae5.signed-trygon-HTJ85B-from-HMJ37.19dea2ba.zip
7a15c95f18ba.signed-trygon-HLK75-from-HLK42B.7a15c95f.zip
7ac6aeb09117.signed-trygon-HLK75D-from-HLK75C.7ac6aeb0.zip
a5de99b3e437.signed-trygon-HMJ37-from-HRI66.a5de99b3.zip
In HMJ37 from HRI66 (3.0.1 to 3.1) I see a bootloader.bin along with this in the updater-script
Code:
assert(package_extract_file("bootloader.bin", "/tmp/bootloader.bin"),
moto.set_mbm_update("/tmp/bootloader.bin"),
delete("/tmp/bootloader.bin"));
There is nothing else that does an "set_mbm_update" in any of the other updates.
On the upside the md5sum of this bootloader.bin matches my own dd dump of the ebb partition.
Code:
c3a74df4a356c0e4158fd592cc8be693 bootloader.img
c3a74df4a356c0e4158fd592cc8be693 /tmp/updates/bootloader.bin
I'd be interested to see if someone can take a dump of their ebb partition as I documented earlier and see if the md5sum matches. if it does, then we will know the bootloader is not the problem. If not, then this is something new to try. Basically we need the dump and then an update.zip to flash it. If someone can provide the dd dump then I can make the update.zip. That should be safe enough to flash I think.

HLK75D for Verizon 4g posted at motor dev!!

I believe this is what everyone is looking for.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
Sent from my Xoom using xda premium

It says it's for MZ602. Will this still work with our current XOOMs.
Furthermore, will it work with a 3G XOOM that has yet to be upgraded?

It says Verizon. It is the same file we updated to. Ours was the mz600, but after the upgrade it became mz602. You know of any other Verizon xoom with 4g? They are going to sell the same xoom, just has the lte card in it this time.
Sent from my Xoom using xda premium

Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."

Thanks... Anybody knows if I flash one of the latinamerican image into a US 4G would brick the Xoom?

I think you have to extract it or unzip it.
Sent from my Xoom using xda premium

hammer4203 said:
I think you have to extract it or unzip it.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.

Great. After using this, my Xoom won't go past the boot screen.
It won't even boot into recovery. I can still access Fastboot and RSD.
Even after trying different unbrick solutions. Even after flashing back to HRI66.
Can't even get my Xoom to turn off now.

You may need the other cable to flash it in rsd mode. There is a special cable that looks exactly like the normal usb cable. It's wired different.
Sent from my ADR6400L using xda premium

You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium

hammer4203 said:
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Yeah.. That's what I'm doing it with. The stock USB cable included with the Xoom and RSDLite v5.4.4 with all the updated drivers.
My Xoom just sits there at the boot screen now, like I said, even after trying to flash back down to HRI66 afterwards to fix it.
I can still boot into Fastboot and RSD mode, but my Xoom stalls and doesn't enter recovery, even after trying another recovery img.
I thought I read something about needing a proper boot.img to go with the SBF file, but I even tried flashing AceXMachine's boot img and nothing.

So you guys haven't gotten this to work or are you just the lucky ones who had problems?

There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium

dethrok said:
Well, I'm having trouble with it.
I'm using RSDLite and trying to flash the .SBF and it's saying:
"Error validating image files" under status, before I even hit start.
Then afterwards, I get:
"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
Click to expand...
Click to collapse
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.

hammer4203 said:
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
zone23 said:
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
Click to expand...
Click to collapse
Find and download RSDLite 5.4.4. That's what fixed it for me.

dethrok said:
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
Click to expand...
Click to collapse
dethrok, you've got most of it right >extract the .SBF (I've had issues on 64 bit Win 7 machine, unless I've place the file at either the root of C: or else under c:\users\<my username>\ (??-weird??))
> make sure you have the latest drivers
> (this is the gotcha) you need to use RSDLite v5.4.4
>>Note: Yes the HLK75D SBF works and was designed with the original MZ600
Hardware, since the MZ602 is just the MZ600 w/ LTE
This should do it for you, however for good measure, I aways run a short script that unlocks, erases (boot/sys/rec/uda & cache partitions), flashes HR166 back onto the device & then relocks it. I know this is probably a waste of time; it just seems to SBF with less issues.
Here's the text out of the .bat I wrote:
(!!!Please bear in mind this will erase/format your device, so please make sure you have all personal data backed up.!!!)
If your system is already powered up and has USB debugging enabled you can remove the 1st REM statement & just execute the .bat file, otherwise reboot the device by holding down the volume up and power button > release both and then hold down the volume down button until the "fastboot" screen appears.
Copy the below text into notepad and save as a .bat file
REM adb reboot bootloader
fastboot oem unlock
REM Press and hold the volume down button
pause
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot -w
pause
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you want to use this, you need to d/l the HRI66 build .img files from MotoDEV as well as having the
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
* you can also just REM out the fastboot commands that flash the HR166 image, so the device is completely blank and you can just load the HLK75D sbf via RSDLite, either way works........
** Remember after any OS flash, you should launch “Android recovery Mode” (press & release the down volume button after the red Motorola symbol appears when the device powers on) and reset the device to factory defaults.
Cheers,
Hat

That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium

hammer4203 said:
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Now see, someone mentioned the other file included in that old .SBF, but no one ever answered as to what to do with it:
janjan said:
Do we need to flash both of these following?
1: 1.35-everest.reflash.sbf
2: VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
And what is 1.35-everest.reflash.sbf is for?
thanks
Click to expand...
Click to collapse
Actually, another person in that thread said they flashed the file first, rebooted, then flashed the .SBF. So I'm not sure anymore.

dethrok said:
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.
And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.
Find and download RSDLite 5.4.4. That's what fixed it for me.
Click to expand...
Click to collapse
Thanks a lot guy that worked and I'm now back in business. Meaning my 3G is now operational. Don't have 4G in my area but I assume it works now as well. My device was unlocked and when I go into network now it shows CDMA/LTE.
Edit:
I did not have the official Xoom cable either.

Zone, did you flash the HLK75D SBF?

Nexus 7 bootloader

In trying to root my Nexus 7 (the new model second generation) I got the bootloader unlocked but when putting in fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.ing I'm getting this message fastboot is not a recognized as internal or external command. I had all files download I spent hours trying to do it and keep getting that same message I tried on 2 different computers so I'm just going to give up. With the bootloader unlocked will I still get and be able to install updates? Is there any downside to leaving it unlocked?
Sent from my SGH-T889 using xda app-developers app

Never mind I think I posted this on the wrong place I re posted it in the right place (I hope)
Sent from my SGH-T889 using xda app-developers app

carlgraser said:
In trying to root my Nexus 7 (the new model second generation) I got the bootloader unlocked but when putting in fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.ing I'm getting this message fastboot is not a recognized as internal or external command. I had all files download I spent hours trying to do it and keep getting that same message I tried on 2 different computers so I'm just going to give up. With the bootloader unlocked will I still get and be able to install updates? Is there any downside to leaving it unlocked?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Check out this post. Should get you going in the right direction. Just remember you have to have the tablet in fastboot for those commands to work. This post gives you a zip that has all the files you need. You can just work from that folder with fastboot. That is basically how I do it...hope it helps. :good:
http://forum.xda-developers.com/showthread.php?t=2150251
carlgraser said:
Never mind I think I posted this on the wrong place I re posted it in the right place (I hope)
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
If you're using the second generation N7, you're in the wrong place. You need to be here:
http://forum.xda-developers.com/forumdisplay.php?f=2407&nocache=1&z=5688943195663757

Bricked nexus 10? Help mee

Okay So I unlocked bootloader via NRT..
So after unlocking I got into recovery and earsed the data(as mentioned in the instructions)..
Now basically the tablet doesn't boot up to home.

First. Dont use toolkits. No disrespect to the dev but it is way better to do it manually.
Second which recovery did you use?
Third what exactly did you wipe?
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
First. Dont use toolkits. No disrespect to the dev but it is way better to do it manually.
Second which recovery did you use?
Third what exactly did you wipe?
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I wiped everything..
There is no OS in my tablet now.. :/

theserpent said:
Okay So I unlocked bootloader via NRT..
So after unlocking I got into recovery and earsed the data(as mentioned in the instructions)..
Now basically the tablet doesn't boot up to home.
Click to expand...
Click to collapse
You can re install the rom by going to https://developers.google.com/android/nexus/images#mantaraykot49h and picking the image you need.
Just hold the power button and the both volume buttons down at the same time to get into the fastboot mode before you run the image restore
program. I hope this helps. Good Luck
Make sure you go down to the Factory Images "mantaray" for Nexus 10.

braider said:
You can re install the rom by going to https://developers.google.com/android/nexus/images#mantaraykot49h and picking the image you need.
Just hold the power button and the both volume buttons down at the same time to get into the fastboot mode before you run the image restore
program. I hope this helps. Good Luck
Make sure you go down to the Factory Images "mantaray" for Nexus 10.
Click to expand...
Click to collapse
I'm sorry im a complete noob in all this..
Sorry to trouble you,but how do I
run the image restore
program
Click to expand...
Click to collapse

You download the file from Google and unzip the *.tgz into a folder on the computer, then you run the flash-all.bat from the folder you unzipped the file in.
Sent from my Nexus 10 using xda app-developers app

Good advice but for a noob needs a bit more about being in command line with the adb and fastboot commands in path. I use Linux desktop. I bricked a n7 last week due to a dodgy connector socket/cable during a flash and had to type the flash-all script commands myself a few times til it worked.
Sent from my Nexus 4 using Tapatalk

braider said:
You download the file from Google and unzip the *.tgz into a folder on the computer, then you run the flash-all.bat from the folder you unzipped the file in.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Okay,Did that But sending system is not completing at all,I waited for like 2-3 hours No USE :/

theserpent said:
Okay,Did that But sending system is not completing at all,I waited for like 2-3 hours No USE :/
Click to expand...
Click to collapse
On my bricked N7 I pulled cable reinserted and retried. Keep retrying each command in the script. Worked eventually for me.

nigelhealy said:
On my bricked N7 I pulled cable reinserted and retried. Keep retrying each command in the script. Worked eventually for me.
Click to expand...
Click to collapse
Will give it a few last trys.
Last option,I'll send my nexus 10 with my uncle back to USA.
Will they charge to fix it?

Hi,
You may want to seek for the guide in the Nexus 10 Q&A regarding flashing stock again.
Can you please go a little further in details about how "bricked" it actually is? What exactly happened? There seem to be missing some important info regarding your issue.
Please be a little more descriptive and maybe I can help you .
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1

Thanks for all the help guys,The tablet booted

i'm ok
the same problem, but perfect, i see the reply, and my device is ok new!:good::good:

[Q] Motorola Droid Razr M stuck on boot animation after 4.4.2 183.46.15 firmware

I have upgraded my razr m on the latest update of Stock KitKat 4.4.2 183.46.15 firmware via RSDLite. Everything gone perfect but on rebooting the device, Motorola logo stayed for quiet a long time and then the droid eye boot animation comes with whole screen flickered two to 3 times then a message on the screen as android is upgrading until 90/90 apps done. When finished loading tons of pop up arises with NFC has stopped, system has stopped, gapps has stopped etc and that's the end, no further moment. On rebooting the device it stuck on droid eye animation no movement forward please help.

Re-flash firmware.
Sent from my XT1031

ATTACK said:
Re-flash firmware.
Sent from my XT1031
Click to expand...
Click to collapse
I have re-flashed the firmware multiple times and downloaded the firmware files from 3 sources, still same problem

Alee_Khan said:
I have re-flashed the firmware multiple times and downloaded the firmware files from 3 sources, still same problem
Click to expand...
Click to collapse
How did you reflash it (what tool)? Have you wiped data? Cache?
Sent from my Moto X 2014 Pure Edition using Tapatalk

xKroniK13x said:
How did you reflash it (what tool)? Have you wiped data? Cache?
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
i have used RSD Lite 6.1.5 and modified the XML file, did everything as instructed, in fact no problem faced during flashing process, just after flash it stuck on boot animation

Go to my thread, scroll down to #4, download and use "House of Moto" to re-flash the firmware.
http://forum.xda-developers.com/showthread.php?t=2869432
Sent from my XT1031

ATTACK said:
Go to my thread, scroll down to #4, download and use "House of Moto" to re-flash the firmware.
http://forum.xda-developers.com/showthread.php?t=2869432
Sent from my XT1031
Click to expand...
Click to collapse
I have downloaded the "House of Moto" and set up everything but it says file not found

Alee_Khan said:
I have downloaded the "House of Moto" and set up everything but it says file not found
Click to expand...
Click to collapse
SamuriHL's House of Moto [xt907] 2.0
FXZ: FXZ_xt907
FLASH MODE: FASTBOOT
Choose option:
File Not Found
C) Change Flash Mode
P) Change Phone Model
E) Exit
Please make a selection:
this is the response of House of Moto

Alee_Khan said:
SamuriHL's House of Moto [xt907] 2.0
FXZ: FXZ_xt907
FLASH MODE: FASTBOOT
Choose option:
File Not Found
C) Change Flash Mode
P) Change Phone Model
E) Exit
Please make a selection:
this is the response of House of Moto
Click to expand...
Click to collapse
I personally haven't used House of Moto, as RSDLite has always worked for me. But users have reported that when RSDLite doesn't work, House of Moto does. So maybe someone with more experience using House of Moto could chime in and help.
Sent from my XT1031

Alee_Khan said:
SamuriHL's House of Moto [xt907] 2.0
FXZ: FXZ_xt907
FLASH MODE: FASTBOOT
Choose option:
File Not Found
C) Change Flash Mode
P) Change Phone Model
E) Exit
Please make a selection:
this is the response of House of Moto
Click to expand...
Click to collapse
If it says file not found, it was not setup properly. Could you walk me through step by step how you set it up? HoM works wonders.
Sent from my Moto X 2014 Pure Edition using Tapatalk

^^^ Correct. Also, is your Java set up correctly?
Sent from my Nexus 5

xKroniK13x said:
If it says file not found, it was not setup properly. Could you walk me through step by step how you set it up? HoM works wonders.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
Thanks for your cooperation! I have flashed the firmware using House of Moto via RSD, but still no success. I have referred to the technician of the device, he said it's a hardware issue, pointing the processor.....may be it is :/

Alee_Khan said:
Thanks for your cooperation! I have flashed the firmware using House of Moto via RSD, but still no success. I have referred to the technician of the device, he said it's a hardware issue, pointing the processor.....may be it is :/
Click to expand...
Click to collapse
A bad processor wouldn't make house of moto throw a file not found error. Did you get HoM working, or did it throw a different error now?
Sent from my Moto X 2014 Pure Edition using Tapatalk

Probably a failing eMMC.
Sent from my XT1031

xKroniK13x said:
A bad processor wouldn't make house of moto throw a file not found error. Did you get HoM working, or did it throw a different error now?
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
No house of moto is working properly but one thing i need to know is what's the difference between normal RSD flash anda HoM RSD flash? Infact the RSD folder in the HoM has bunch of other files so i am confused what's the main difference between these two, as both have same working.

ATTACK said:
Probably a failing eMMC.
Sent from my XT1031
Click to expand...
Click to collapse
Yeah he also pointed the eMMC failed issue

can we format emmc using any tool because cant install recovery on it, or tell me how to format system.img on xt907 using fastboot or any, without recovery

Alee_Khan said:
can we format emmc using any tool because cant install recovery on it, or tell me how to format system.img on xt907 using fastboot or any, without recovery
Click to expand...
Click to collapse
If it is your eMMC failing, there's nothing that can be done. You'll need a new phone.
Sent from my XT1031

ATTACK said:
If it is your eMMC failing, there's nothing that can be done. You'll need a new phone.
Sent from my XT1031
Click to expand...
Click to collapse
please tell me any method to format system from phone,

Alee_Khan said:
please tell me any method to format system from phone,
Click to expand...
Click to collapse
Using fastboot type:
Code:
fastboot format system
EDIT: Wait, from your phone? Like, without a PC? Can't be done
Sent from my XT1031