I was rooted and removed some of the bloatware, before applying this update I reinstalled the bloatware and unrooted, when I try to update(5.6.980) it goes through but hangs on updating bp then it says
assert failed: motorola.motoflash("/tmp/bp.img")
E:Error in /tmp/sideload/package.zip
(status 7)
installation aborted
...idk what to do I tried wiping, rooting then unrooting and I keep getting the sam message and I guess thats needed for radio because now my phone can't find it, is there a package file or something i need????????????
anybody....
LRiley said:
anybody....
Click to expand...
Click to collapse
Have you tried flashing bp.img in fastboot?
rynosaur said:
Have you tried flashing bp.img in fastboot?
Click to expand...
Click to collapse
how do I do that?
LRiley said:
how do I do that?
Click to expand...
Click to collapse
I think this will be the file you need.
Then, get fastboot and put that file in the same directory.
Put the phone in AP Flash mode.
Connect with Moto cable to a good USB port.
type in:
Code:
fastboot devices
and verify that your device is shown without restrictions (you'll see a 16-char HEX code/serial id#)
if windows:
Code:
.\fastboot flash bpsw bpsw.img
if linux/unix/Mac:
Code:
./fastboot flash bpsw bpsw.img
reboot into recovery then try the update again.
did it and it says sending, OKAY, writing, (bootloader) command restricted, FAILED...is that right?
LRiley said:
did it and it says sending, OKAY, writing, (bootloader) command restricted, FAILED...is that right?
Click to expand...
Click to collapse
Well, yes, probably. For some reason, only certain partitions are available to flash from AP Fastboot.
rynosaur said:
Well, yes, probably. For some reason, only certain partitions are available to flash from AP Fastboot.
Click to expand...
Click to collapse
no, that means nothing happened. It sent it to the device, but didnt write it. So right where you started.
I got the same error again, I'm gonna root and try again
edru said:
no, that means nothing happened. It sent it to the device, but didnt write it. So right where you started.
Click to expand...
Click to collapse
Well, yeah, that's what I meant. It's normal for that partition to fail out. I'm guessing certain blocks can only be written in raw form from BP/SBF.
now I'm stuck in fastboot wut do I do now
LRiley said:
now I'm stuck in fastboot wut do I do now
Click to expand...
Click to collapse
Stuck? Reflash a non-protected partition, like cdrom. Then.
Code:
fastboot reboot
did it with mdm, but I'm back to square one
In the future, you'll probably get more help by titling your thread something more useful. I have skipped over it a few times already.
What's the output of
Code:
df /system
Edit: scratch that. bp.img is extracted to /tmp, which I'm guessing is a RAM disk. Have you tried running the update again? I'm not sure I understand why it would fail. Regardless, it is flashed using a Motorola utility so I imagine flashing by fastboot won't work.
I flashed it a lot of times but the update always gets stuck at bp
any ideas?
Can you post /cache/recovery/last_log
limaxray said:
Can you post /cache/recovery/last_log
Click to expand...
Click to collapse
where do I get that
LRiley said:
where do I get that
Click to expand...
Click to collapse
I assume you have adb installed? In a terminal, run:
Code:
adb shell
su
cp /cache/recovery/last_log /sdcard/
exit
exit
adb pull /sdcard/last_log <some local directory>
Replacing <some local directory> with wherever is convenient.
Related
Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.
Edit: nvm
Here is the dump. Thanks for your work.
KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?
I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.
Glad I could help. Now folks have less things to worry about when they decide to root
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.
efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).
For science
KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.
When i try to push a file or rom on my htc one using sideload, it says "failed" i am currently left out without operating system and evrything wiped out of my device. please help
AHMEDNATOR said:
When i try to push a file or rom on my htc one using sideload, it says "failed" i am currently left out without operating system and evrything wiped out of my device. please help
Click to expand...
Click to collapse
what is your adb version? Have you tried adb push instead of adb sideload?
i dont know what version it is and i am using the squabbi htc toolkit, ive tried push but i didnt get any results
AHMEDNATOR said:
i dont know what version it is and i am using the squabbi htc toolkit, ive tried push but i didnt get any results
Click to expand...
Click to collapse
So let start at the beginning:
Don't use toolkit, use adb and fastboot directly from the command prompt
go there: http://forum.xda-developers.com/showthread.php?t=2317790
follow instructions in above thread to install minimal abd and fastboot on your computer
alray said:
what is your adb version? Have you tried adb push instead of adb sideload?
Click to expand...
Click to collapse
i dont know what adb version i have but ive tried using push with the squabbi htc too, no result in the end or i ll say failed protocol or whatever
AHMEDNATOR said:
i dont know what adb version i have but ive tried using push with the squabbi htc too, no result in the end or i ll say failed protocol or whatever
Click to expand...
Click to collapse
listen mate, I'm ready to help you push or sideload a rom to your phone, but we will not use this toolkit (no disrespect to squabbi btw).
When things goes wrong, better to use adb/fastboot directly from terminal, not using a toolkit.
so go ahead and install adb/fastboot on your computer so we can start troubleshooting.
alray said:
So let start at the beginning:
Don't use toolkit, use adb and fastboot directly from the command prompt
go there: http://forum.xda-developers.com/showthread.php?t=2317790
follow instructions in above thread to install minimal abd and fastboot on your computer
Click to expand...
Click to collapse
ok i am doing as you say, when i am done with this first step, i ll write here. btw my internal memory seems to be completely wiped out as i see 0mb in every folder via TWRP. Please can i add you up on facebook because i have to wait up to five minutes here to reply to you because i am new, it ll go faster on facebook
AHMEDNATOR said:
my internal memory seems to be completely wiped out as i see 0mb in every folder via TWRP.
Click to expand...
Click to collapse
In twrp, when you click on ''install'' does it says ''storage: internal storage: (0 MB)''? If it says 0 MB then you probably have corrupted your data partition...
Please can i add you up on facebook because i have to wait up to five minutes here to reply to you because i am new, it ll go faster on facebook
Click to expand...
Click to collapse
Irc, this restriction only apply for the first 10 posts, only 2 more and you'll get rid of it.
yes it is corrupted i guess, what can i do to fix this problem?
alray said:
In twrp, when you click on ''install'' does it says ''storage: internal storage: (0 MB)''? If it says 0 MB then you probably have corrupted your data partition...
Irc, this restriction only apply for the first 10 posts, only 2 more and you'll get rid of it.
Click to expand...
Click to collapse
yes it is corrupted i guess, what can i do to fix this problem?
AHMEDNATOR said:
yes it is corrupted i guess
Click to expand...
Click to collapse
does it says: ''storage: internal storage: (0 MB)''
Yes or No?
''I guess'' is not enough
in twrp, when you click on ''install'' does it says ''storage: internal storage: (0 MB)''?
Click to expand...
Click to collapse
alray said:
does it says: ''storage: internal storage: (0 MB)''
Yes or No?
''I guess'' is not enough
Click to expand...
Click to collapse
yes sadly
AHMEDNATOR said:
yes sadly
Click to expand...
Click to collapse
ok so you'll need to format your data partition
in twrp, select ''wipe'' then ''format data''
alray said:
ok so you'll need to format your data partition
in twrp, select ''wipe'' then ''format data''
Click to expand...
Click to collapse
ok done mate! what now?
btw, what version of twrp are you using?
alray said:
btw, what version of twrp are you using?
Click to expand...
Click to collapse
v2.6.3.0
AHMEDNATOR said:
ok done mate! what now?
Click to expand...
Click to collapse
This part to do in 2nd - in recovery mode:
make sure your rom.zip is in the same folder of adb and fastboot, if you have installed minimal adb and fastboot, it should be C:\Program\Minimal ADB and Fastboot\
hold shift + right click a blank space in that folder, select ''start command prompt here'' from the contextual menu.
then in the command prompt (with your phone booted in twrp) type:
Code:
adb devices
it should reply your device s/n + recovery, If yes then:
Code:
adb push name_of_rom.zip /sdcard/
should take around 5 min to transfer (there is no progress bar)
---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------
AHMEDNATOR said:
v2.6.3.0
Click to expand...
Click to collapse
This part to do 1st in bootloader mode (fastboot usb mode)
wait your twrp is outdated and most newer rom require at least twrp 2.6.3.3.
download and save twrp 2.6.3.3 to your adb/fastboot folder
with phone in bootloader mode (fastboot):
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then re-enter recovery and do what I said above
should my phone be in recovery mode or [email protected]
AHMEDNATOR said:
should my phone be in recovery mode or [email protected]
Click to expand...
Click to collapse
see above post, edited in red
@alray where should the adb fastboot folder be located? is it supposed to show up when i plug in my phone?
So attempting to flash the M Preview and i got the missing system.img error when using the flash-all command.
I attempted to flash the files one by one and got this error on the first file
error cannot load bootloader-shamu-moto-apq8084-71.11
im sure the answer is right in front of me but I can' figure out what im doing wrong
twostep665 said:
So attempting to flash the M Preview and i got the missing system.img error when using the flash-all command.
I attempted to flash the files one by one and got this error on the first file
error cannot load bootloader-shamu-moto-apq8084-71.11
im sure the answer is right in front of me but I can' figure out what im doing wrong
Click to expand...
Click to collapse
What was the exact command as you typed it?
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11
twostep665 said:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11
Click to expand...
Click to collapse
When you type
fastboot devices
Does is your device recognized?
cam30era said:
When you type
fastboot devices
Does is your device recognized?
Click to expand...
Click to collapse
yep... I actually had this problem the other day as well when trying to flash 5.1.1 factory image as well
twostep665 said:
yep
Click to expand...
Click to collapse
Well, I'm not sure what to tell you....
twostep665 said:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11
Click to expand...
Click to collapse
Did you type ".img" at the end of that command? (without quotes)
Evolution_Tech said:
Did you type ".img" at the end of that command? (without quotes)
Click to expand...
Click to collapse
i tried both ways. with .img at the end and without. both got the same error msg.
twostep665 said:
i tried both ways. with .img at the end and without. both got the same error msg.
Click to expand...
Click to collapse
SDK updated?
Evolution_Tech said:
SDK updated?
Click to expand...
Click to collapse
Aahh. Good point. With a totally new version of Android, that makes sense!
cam30era said:
Aahh. Good point. With a totally new version of Android, that makes sense!
Click to expand...
Click to collapse
I will give that a shot. Thanks.
twostep665 said:
I will give that a shot. Thanks.
Click to expand...
Click to collapse
Also double check and make sure you are typing the file name exactly as it is written, including .img at the end.
cam30era said:
Also double check and make sure you are typing the file name exactly as it is written, including .img at the end.
Click to expand...
Click to collapse
Yep and to expand on this, make sure windows is set to show file extensions and when in doubt, rename complicated named files to be simple whisky remaining descriptive.
rootSU said:
when in doubt, rename complicated named files to be simple whisky remaining descriptive.
Click to expand...
Click to collapse
Like Glenmorangie or Laphroaig?
cam30era said:
Like Glenmorangie or Laphroaig?
Click to expand...
Click to collapse
No, silly. Like Caol Ila, Lagavulin or Bruichladdich - but good effort
rootSU said:
No, silly. Like Caol Ila, Lagavulin or Bruichladdich - but good effort
Click to expand...
Click to collapse
hahaha. Thanks everyone for the help. I got it working last night. Updating the SDK seemed to do the trick.
twostep665 said:
hahaha. Thanks everyone for the help. I got it working last night. Updating the SDK seemed to do the trick.
Click to expand...
Click to collapse
Glad you got it solved.
I had an issue getting the M preview installed as well. Kept failing when trying to
Code:
fastboot -w update image-shamu-MPZ44Q.zip
. Ended up wiping my internal storage and I was in a bit of a pickle so heres what I did: (you need to start off in bootloader mode)
1. Download twrp from HERE
2. Then go to where you downloaded the file and flash it (since I'm using Ubuntu it's in "Downloads")
Code:
cd Downloads && fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu.img
3. When the recovery finishes flashing manually reboot to recovery from the device by pressing the volume up key then press power to select "Recovery"
4. In TWRP go to the "mount" section and make sure that "system" is selected if it isn't. Then reboot to bootloader (if you get the "No OS error" don't worry, just disregard and ignore the SU flash prompt.
5. Now that your system has been re mounted you can manually flash each file but incase you want a copy and paste here it is:
(also make sure you unzip the image-shamu-MPZ44Q.zip file to extract the image-shamu-MPZ44Q folder)
-1
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11.img
-2 reboot bootloader
-3
Code:
fastboot flash radio radio-shamu-D4.01-9625-05.16+FSG-9625-02.94.img
-4 reboot bootloader
-5
Code:
cd image-shamu-MPZ44Q && fastboot flash system system.img && fastboot flash boot boot.img && fastboot flash cache cache.img && fastboot flash userdata userdata.img && fastboot flash recovery recovery.img && fastboot reboot
PROFIT!
Hi there!
I have a TX1085, it is already unlocked and rooted and has the CM Recovery installed. But before the CM Recovery I had the TWRP Recovery installed and tried to use it to flash CM12, which I had put on the SD-Card. It kept on telling me that mounting the system failed. Unfortunately I wiped everything via TWRP Recovery without creating a backup. Then I installed the CM Recovery to try again. Now, if I try to flash via CM Recovery (apply update) it doesn't show anything in my internal storage and I can't connect via adb using Ubuntu (Terminal tells me either "device not found" or "device offline".)
Any suggestions?
Greets
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
psssss said:
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
Click to expand...
Click to collapse
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
pyq said:
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
Click to expand...
Click to collapse
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
josuearisty said:
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
pyq said:
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
Click to expand...
Click to collapse
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
Click to expand...
Click to collapse
I am using Linux without Android SDK, but I have working fastboot and adb installed.
josuearisty said:
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
try to flash stock firmware
kaktusmaier125 said:
try to flash stock firmware
Click to expand...
Click to collapse
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Click to expand...
Click to collapse
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
josuearisty said:
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
pyq said:
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
Click to expand...
Click to collapse
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
josuearisty said:
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
If I use the "fastboot boot CM_recovery.img" command the phone installs it and then starts into TWRP. Except for that nothing changes. How can I continue?
rotorbudd said:
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
Click to expand...
Click to collapse
If I try to make a tick (as to mount) system the phone vibrates but doesn't tick system, so I can't mount it this way.
pyq said:
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
Click to expand...
Click to collapse
Yes you can
My device unexpectedly got stuck on the boot screen. I have a replacement device on the way but want to pull as many files off the devices as possible. I can get into recovery mode and have the option to apply update from ADB. When I open the command terminal from ADB, "adb devices" returns an error that "adb" is not recognized. However, when I input ".\adb devices" a device is listed with "sideload", however, trying to pull /sdcard/ returns a closed connection. I would looooovve any help.
Hi,
You should have posted this on the questions and answers section.
If you can get to recovery, I'm guessing you can get to the bootloader.
While on the bootloader type "fastboot reboot fastboot"
That should get you to fastbootd.
There you should have adb access.
Sideloading the latest ota update may help. Or what's worked for me is sideloading the the ota for a different carrier. Or go to bootloader and flash the system image, after deleting the -w in the flash-all file.
That should let you boot up.
mistermojorizin said:
Sideloading the latest ota update may help. Or what's worked for me is sideloading the the ota for a different carrier. Or go to bootloader and flash the system image, after deleting the -w in the flash-all file.
That should let you boot up.
Click to expand...
Click to collapse
I just tried sideloading three different OTAs but got an error "failed to read command: No error" at 94% for all of them.
There's a warning before downloading system images that flashing will delete all the files. Is this true?
Listentothis said:
I just tried sideloading three different OTAs but got an error "failed to read command: No error" at 94% for all of them.
There's a warning before downloading system images that flashing will delete all the files. Is this true?
Click to expand...
Click to collapse
The 94 percent and that error is normal. Did you try to boot after? Guess that didn't work?
For the factory image, you have to delete the -w as I mentioned, or yes it will wipe.
mistermojorizin said:
The 94 percent and that error is normal. Did you try to boot after? Guess that didn't work?
For the factory image, you have to delete the -w as I mentioned, or yes it will wipe.
Click to expand...
Click to collapse
I did try booting after and it's still stuck on the boot screen. \:
Can you please explain how to remove the -w from the flash-all file? I don't see it in the file name or when I open the file.
Listentothis said:
I did try booting after and it's still stuck on the boot screen. \:
Can you please explain how to remove the -w from the flash-all file? I don't see it in the file name or when I open the file.
Click to expand...
Click to collapse
Edit the flash all.bat file with something like text editor++. The last line or so has the wipe command that needs to be removed.