Related
So I tried flashing back to stock tonight, and it all went wrong. Here are the steps I took and rationale behind them:
1. Tried using RSD lite 6.15 with the FXZ file. RSD didn't recognize my phone at all
2. I updated fastboot/adb but still wouldnt recognize the device
3. Went into fastboot and tried to flash there
3a. Using instructions I saw in this thread, I flashed the files contained inside of the FXZ file within fastboot
4. Everything was fine, but once I got to system.img, the file size was apparently bigger than the actual partition allows? It crashed fastboot entirely. Doesn't even finish the resulting string of text before it cuts off. See the picture below.
So now, I sit with a Moto X with no system partition, a wiped internal storage. Someone help please?
EDIT: Got it to boot by flashing the system.img from AT&T FXZ file!
Seems strange really. The system.img from the VZW FXZ file is too big to actually flash in fastboot..... I'm never going to understand why but I'll go with it I guess. Now I'm stuck on custom roms since data and wifi doesn't work with the AT&T stock system.img
Ignore all of this, I was just really careless and didn't see my mistake. Download this and rename it fastboot.exe and replace the original fastboot with it. You then will have no problems at all flashing system.img
alex94kumar said:
So I tried flashing back to stock tonight, and it all went wrong. Here are the steps I took and rationale behind them:
1. Tried using RSD lite 6.15 with the FXZ file. RSD didn't recognize my phone at all
2. I updated fastboot/adb but still wouldnt recognize the device
3. Went into fastboot and tried to flash there
3a. Using instructions I saw in this thread, I flashed the files contained inside of the FXZ file within fastboot
4. Everything was fine, but once I got to system.img, the file size was apparently bigger than the actual partition allows? It crashed fastboot entirely. Doesn't even finish the resulting string of text before it cuts off. See the picture below.
So now, I sit with a Moto X with no system partition, a wiped internal storage. Someone help please?
EDIT: Got it to boot by flashing the system.img from AT&T FXZ file!
Seems strange really. The system.img from the VZW FXZ file is too big to actually flash in fastboot..... I'm never going to understand why but I'll go with it I guess. Now I'm stuck on custom roms since data and wifi doesn't work with the AT&T stock system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249
I have ran rsd and fastbooted the system.IMG quite a few times I've never had any issues with it. I'm on the consumer edition vzw x
---------- Post added at 07:00 PM ---------- Previous post was at 06:55 PM ----------
There is a nice debloated, deodexed vzw ROM on droidrzr.com made by t3droid
shane1 said:
I have ran rsd and fastbooted the system.IMG quite a few times I've never had any issues with it. I'm on the consumer edition vzw x
---------- Post added at 07:00 PM ---------- Previous post was at 06:55 PM ----------
There is a nice debloated, deodexed vzw ROM on droidrzr.com made by t3droid
Click to expand...
Click to collapse
rsd breaks it apart for you in the process so you don't have to. The system image from sbf fxz is too large for the vzw x to flash. You get a too large of a file size error. This mfastboot in the link above splits the file up for you. Don't know what image you were flashing before if you were doing it manually but the size of the stock FW image is too large on Vzw... Other people have the problem as well.
I pulled the system.IMG from the fxz from sbf droid developers. And I fastbooted it probably at least 20 times last weekend. I was having some issues lol
shane1 said:
I pulled the system.IMG from the fxz from sbf droid developers. And I fastbooted it probably at least 20 times last weekend. I was having some issues lol
Click to expand...
Click to collapse
i believe if you are using the fastboot that is in the fxz files, that fastboot has it built in as well. if you are using the one from sdk platform tools then it does not
i was unaware the fxz's had fastboot. i got from sdk but what evs.
alex94kumar said:
So I tried flashing back to stock tonight, and it all went wrong. Here are the steps I took and rationale behind them:
1. Tried using RSD lite 6.15 with the FXZ file. RSD didn't recognize my phone at all
2. I updated fastboot/adb but still wouldnt recognize the device
3. Went into fastboot and tried to flash there
3a. Using instructions I saw in this thread, I flashed the files contained inside of the FXZ file within fastboot
4. Everything was fine, but once I got to system.img, the file size was apparently bigger than the actual partition allows? It crashed fastboot entirely. Doesn't even finish the resulting string of text before it cuts off. See the picture below.
So now, I sit with a Moto X with no system partition, a wiped internal storage. Someone help please?
EDIT: Got it to boot by flashing the system.img from AT&T FXZ file!
Seems strange really. The system.img from the VZW FXZ file is too big to actually flash in fastboot..... I'm never going to understand why but I'll go with it I guess. Now I'm stuck on custom roms since data and wifi doesn't work with the AT&T stock system.img
Ignore all of this, I was just really careless and didn't see my mistake. Download this and rename it fastboot.exe and replace the original fastboot with it. You then will have no problems at all flashing system.img
Click to expand...
Click to collapse
Very thanks
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?
I'm currently using twrp 2.6 but getting ready to switch to the twrp 2.7 available in this article, (
http://www.androidpolice.com/2014/06/10/moto-x-finally-gets-official-build-of-twrp-custom-recovery/
),
But I'm wondering if u should switch to cwm for any reason... If so, why? Just looking for feed back...
Also, it's been years since I switched or upgraded recoveries on a phone, (thunderbolt) and I can't remember if I used adb or what method I used at all, aside from installing my current recovery using adb... How would I go about switching?
Sent from my Moto X using Tapatalk
Hammerdroid said:
I'm currently using twrp 2.6 but getting ready to switch to the twrp 2.7 available in this article, (
http://www.androidpolice.com/2014/06/10/moto-x-finally-gets-official-build-of-twrp-custom-recovery/
),
But I'm wondering if u should switch to cwm for any reason... If so, why? Just looking for feed back...
Also, it's been years since I switched or upgraded recoveries on a phone, (thunderbolt) and I can't remember if I used adb or what method I used at all, aside from installing my current recovery using adb... How would I go about switching?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
The vast majority of us are using TWRP.
There are a couple of ways to flash the recovery. You MUST be bootloader-unlocked for either method to work (I'm assuming you are...).
The "Easy" way: You MUST already be rooted. Download Rashr or Flashify (both are confirmed to work on the Moto X), and flash the new recovery .img from within the app.
The "Manual" way: You must have the android SDK and 'mfastboot' binary installed on your PC. You will also need to download the twrp recovery.img file, and place it in the same folder on your PC as 'mfastboot'. You will boot the phone into bootloader mode (AP Fastboot Mode) and from command prompt on your pc type the following command:
mfastboot flash recovery twrp_recovery_file_name.img
Good Luck
I think you may use the regular fastboot.exe for flashing everything but system.img. I know you must use mfastboot for system.img and mfastboot will work for all .img files.
Are either of you familiar with the custom moto x twrp recovery?
Sent from my Moto X using Tapatalk
Groid said:
I think you may use the regular fastboot.exe for flashing everything but system.img. I know you must use mfastboot for system.img and mfastboot will work for all .img files.
Click to expand...
Click to collapse
You are correct. The standard fastboot should work for recovery, but so will mfastboot. We are recommending mfastboot for all flashing to try to avoid those 'I can't flash system.IMG ??' Threads.
If we recommend mfastboot for all flashing operations, we are less likely to have such threads.
Have fun
---------- Post added at 12:48 PM ---------- Previous post was at 12:45 PM ----------
Hammerdroid said:
Are either of you familiar with the custom moto x twrp recovery?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Yes, that is what 90% of us are using.... Unless you are referring to the custom-themed versions. Those should function identical to standard official twrp recovery.
Groid said:
I think you may use the regular fastboot.exe for flashing everything but system.img. I know you must use mfastboot for system.img and mfastboot will work for all .img files.
Click to expand...
Click to collapse
In Theory, yes, fastboot.exe should be able to flash everything by system.img (since Moto's system.img is too big for the standard fastboot to flash).
In practice, in several thread I've seen reports of people trying to flash recovery and logo.bin using the regular fastboot.exe, and while it reported it was successful, the user didn't see the changes reflected. Once they used mfastboot to flash, everything worked as expected.
And that is another reason why I suggest always using mfastboot.
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
doud1998 said:
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
Click to expand...
Click to collapse
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Hazou said:
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Click to expand...
Click to collapse
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
doud1998 said:
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
Click to expand...
Click to collapse
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Hazou said:
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Click to expand...
Click to collapse
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
doud1998 said:
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
Click to expand...
Click to collapse
I meant, in my signature under my post u can find within the link INDEX/GUIDE, ALL Things RAZR I under paragraph/ section E a link to all the firmwares available for the Razr I.
But in this case i will post the full link to the firmware site, here.
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
i tried to flash recovery_signed but i have the error
Checking fs on partition pds...
E:can't repaire partition pds
E:failed to mount PDS partition
doud1998 said:
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
Click to expand...
Click to collapse
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Hazou said:
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Click to expand...
Click to collapse
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
+> i don't have any backup and i can't go to recovery , when it turns on it automaticly stuck to the ap fastboot menu
doud1998 said:
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
Click to expand...
Click to collapse
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
waj3k said:
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
Click to expand...
Click to collapse
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
doud1998 said:
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
Click to expand...
Click to collapse
I know, I just uploaded Deodexed Retail Great Britain ICS:
Here you go. There should be a download icon at the top.
give me the right access (i'm [email protected])
Sorry, forgot to set it to public, should be fixed now.
so now i have to flash the boot.img or what? i'm not really sure what to do with this zip
You need to flash custom recovery and then you can install a zip.
Here is a tutorial on how to use recovery, if you're unsure.
i can't make works neither cwm nor twrp
doud1998 said:
So here is my problem, after trying to install a custom rom on my razr i, i may have broken something in the system
Click to expand...
Click to collapse
may i ask you what u have exactly done to install your "custom rom"?
1. Bootloader unlocked?
2. Custom Recovery installed?
3. How did you installed your rom?
4. Which custom rom?
Here is the a rooted boot and system img (rooted with busybox installed, no other modifications). Stock recovery and the modem
BUILD: LXE22.46-11
Flash in fastboot mode. If you don't know how I suggest you use Google.
To flash the system.img you will need mfastboot found here. https://mega.co.nz/#!4wAkGJxJ!x5O6w-3KzoS4Xedo_gCALNXt5swNEevmENvv4iHBGS4
You will need to split up the system.img to use.. this is for advanced users only..
Download Links can be found on my website: http://www.graffix.nyc/motox.php
DO NOT MIRROR
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
thanks brotha
Just realized that I had Better Battery Stats installed as a system app when I did the system img. I'm uploading a new one now
system.img link is back up
You should put this in the android development section
graffixnyc said:
Just realized that I had Better Battery Stats installed as a system app when I did the system img. I'm uploading a new one now
Click to expand...
Click to collapse
no worries. i always do my own pull of the system.img right after root. recovery.img is something i never pull since that's usually one of the first things readily available in sections due to it's small size and the necessity for having custom recoveries to flash user made zips (and needing to go back for OTAs).
Did you try to use mfastboot or fastboot? On the og moto x you have to use mfastboot to flash the system.
tigercranestyle said:
last edit:
had issue on my end with bad mfastboot. got a copy of v2 and install via mfastboot works.
thx op for files and matt for suggestion.
Click to expand...
Click to collapse
Glad it worked. Do you have a link to the mfastboot you got and I'll add the link to the op
Sent from my XT1095 using Tapatalk
Could anyone help me out? I ran into an issue when trying to flash the system.img. I get the following
errorload_file: could not allocate -1392508928 bytes
error: cannot load 'system.img'
I don't believe I'm doing anything wrong, but can someone please clarify?
Schultz_91 said:
Could anyone help me out? I ran into an issue when trying to flash the system.img. I get the following
errorload_file: could not allocate -1392508928 bytes
error: cannot load 'system.img'
I don't believe I'm doing anything wrong, but can someone please clarify?
Click to expand...
Click to collapse
Did you mfastboot? Must not fastboot for system only.
I did download the mfastboot and extracted it to my C drive. I tried throwing the system.img into that folder and flashing. Is that what you mean? If not could you please elaborate?
---------- Post added at 03:54 AM ---------- Previous post was at 03:37 AM ----------
Aha. I see. mfastboot breaks it up into manageable chunks. When I flashed it the first time I was impatient as it didn't give my any output for a bit. Apologies. Thanks so much!
Thanks so much for posting this! In what order do we flash these. Is there anyone's favorite tutorial out there to help?? Thanks
stu5797 said:
Thanks so much for posting this! In what order do we flash these. Is there anyone's favorite tutorial out there to help?? Thanks
Click to expand...
Click to collapse
It's doesn't matter which order you flash them in. There are plenty of tutorials on how to flash fastboot images, just do a Google search.
Sent from my XT1095 using Tapatalk
graffixnyc said:
Here is a system.img that is rooted with busybox installed (No other modifications), The stock Boot.img and the stock recovery.
BUILD: KXE21.187-42
Flash in fastboot mode. If you don't know how I suggest you use Google.
To flash the system.img you will need mfastboot found here. https://mega.co.nz/#!4wAkGJxJ!x5O6w-3KzoS4Xedo_gCALNXt5swNEevmENvv4iHBGS4
System: https://www.androidfilehost.com/?fid=95747613655040839
MD5:9b4e37afd99a92a69a00a6401023dc2c
Boot: https://www.androidfilehost.com/?fid=95747613655040774
MD5:d8be13fe97e1791023d7031789bf9f65
Recovery: https://www.androidfilehost.com/?fid=95747613655040773
MD5: a5673547c4a78b255cce3c64aa854a2b
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
Click to expand...
Click to collapse
Is there a way to unlock the software restricted LTE bands on the XT1095?
Sent from my A0001 using XDA Free mobile app
graffixnyc said:
Here is a system.img that is rooted with busybox installed (No other modifications), The stock Boot.img and the stock recovery.
BUILD: KXE21.187-42
Flash in fastboot mode. If you don't know how I suggest you use Google.
[/COLOR][/SIZE]
Click to expand...
Click to collapse
Please clarify my doubts...
My build number is same KXE21.187-42, but system version is "21.21.42.........en.EU retin". I did root this and it is working great, installed custom recovery and also xposed framework...
Now if I want stock recovery can I uninstall the Xposed and flash the stock recovery that has been provided here (and of course take an OTA)? Does that depends on build number alone, or something to do with system version also...?
Kindly enlighten me, there may be many posts regarding this issue, but I'm confused and need a confirmation...
ThnQ...
is the DL link dead for anyone else?
flashed the img thru fastboot and now i cant boot up. do not use this.
papi92 said:
flashed the img thru fastboot and now i cant boot up. do not use this.
Click to expand...
Click to collapse
Is your phone the pure edition?
Yes
I've flashed all images with no issue