Database Develop

[WIP] [REQUEST] Misc partition dumps

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.

1.31.651.2 ruu?

Does anyone know when the new ruu for the HTC One comes out? I went to unroot my phone, locked the bootloader, and went to run the ruu, only to realize I did the system update a few days before. So now I'm stuck in a bootloop and I can't mount my sd card ( I think it's corrupted ) So I'm pretty much out of a phone till then, correct?
Thank you in advance guys.

If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium

propjockey said:
If you can unlock again, and somehow get adb to work, you can s-off using revone. Then you can flash any RUU. Otherwise, I dunno
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I re-unlocked the phone again but I have no clue how to do the rest.

If you can get files to your sd, you can run revone or moonshine to get s-off. Look in original development for the corresponding threads and instructions. Once you have that, you can RUU old firmware or unsigned.
Sent from my HTCONE using xda premium

I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.

Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I'm having a similar problem and need some help too!!

tx_jaycee said:
I'm having a similar problem and need some help too!!
Click to expand...
Click to collapse
I think the only thing that will fix our problem is a new version of the ruu. I knowledge on adb is very limited, I'm sure someone that knows what their doing can fix it 1,2,3, but that person isn't me. :crying:

ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.

Rirere said:
ADB should not be your tool of choice. Fastboot would be your friend here, since it's a lot more direct in its method. If your internal card isn't completely hosed, you should be able to restore using the fastboot flash commands to reflash your /system and /boot and /recovery, at which point you should be fine. There are several threads on how to do this.
Click to expand...
Click to collapse
Can you point me in the right direction?

I tried the all in one kit, tells me device not found. I know it's found by my computer, it's in the device manager, plus I hear the noise that confirms a device is found. I can reboot my phone thru the all in one kit. I think it's best to wait for the newest ruu in my case.

Chloroform said:
Can you point me in the right direction?
Click to expand...
Click to collapse
Download the image of your choosing from this thread: http://forum.xda-developers.com/showthread.php?t=2368907.
Download TWRP 2.5 from this thread: http://forum.xda-developers.com/showthread.php?t=2236620.
Put your phone into fastboot mode (power + volume up + volume down). Plug the phone into your computer.
Install fastboot/ADB. You may need to search the web for the platform tools, or there are some toolkits that can help.
Open a command prompt and run "fastboot flash recovery <path-to-recovery.img>".
Go to Advanced -> ADB sideload, then run "adb install <path-to-downloaded-image.zip>".
If that doesn't work, open the zip and run:
fastboot flash system <path-to-system.img>
fastboot flash recovery <path-to-recovery.img>
Bottom line is if you're not willing to learn a bit about fastboot and ADB, then you shouldn't be using a toolkit because you won't be able to fix your device if something goes wrong.

So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?

Chloroform said:
I can't mount my internal storage. Even in TWRP recovery it shows nothing on the sd card. I think some how the internal sd card got corrupted, so I can't mount it.
Click to expand...
Click to collapse
I've had this problem. To correct it, I put everything I need to flash in /sdcard/0. TWRP sometimes only sees stuff within a 0 folder placed inside root.
If you haven't tried already, make a 0 folder on the sdcard, then copy it and see what TWRP shows.

Thank you to @Indirect for fixing my problem.

Chloroform said:
So I pretty much tried everything with no luck BUT I flashed the boot.img and now I'm getting some where. Now it's showing my internal storage but the rom I had installed I guess erased. I've been searching around people saying flash system.img but how can I flash a system.img? All the files I've been finding are .zip and there any .img roms that I can flash?
Click to expand...
Click to collapse
In the future, try extracting your downloaded .zip files.
OTA packages and recovery-flashable ROMs are provided as .zip files. Each archive contains the necessary .img files and a script that tells the recovery where to put them. You can extract these .img files and flash them with fastboot if you don't have recovery access.
Fastboot factory images generally are .img files compressed as .tar files. You'd better have a tool like 7zip onboard so you can deal with the many archive formats you'll find on the net.

Closed per OP request

[Q] htc one no rom

phone is unlocked just need to flash the rom, no recovey no backup nothing, plz help step by step.

if you have no adb; get it from here: http://forum.xda-developers.com/showthread.php?t=2317790
download TWRP recovery from here: http://goo.im/devs/OpenRecovery/m7ul/openrecovery-twrp-2.6.3.4-m7ul.img
place your downloaded recovery file in your adb folder
keep your phone in bootloader/hboot and connect your device to PC
start adb command prompt and type
fastboot devices
Click to expand...
Click to collapse
if your device gets recognized type the following commands:
fastboot erase cache
fastboot flash recovery recovery_file_name.img
Click to expand...
Click to collapse
and done
if you have no ROM inside your SDcard you can sideload it by following this guide

appreciate
kamilmirza said:
if you have no adb; get it from here: http://forum.xda-developers.com/showthread.php?t=2317790
download TWRP recovery from here: http://goo.im/devs/OpenRecovery/m7ul/openrecovery-twrp-2.6.3.4-m7ul.img
place your downloaded recovery file in your adb folder
keep your phone in bootloader/hboot and connect your device to PC
start adb command prompt and type
if your device gets recognized type the following commands:
and done
if you have no ROM inside your SDcard you can sideload it by following this guide
Click to expand...
Click to collapse
let me do this if any problem occurs will let u know...

rom
dsthakur said:
let me do this if any problem occurs will let u know...
Click to expand...
Click to collapse
plz suggest the address(download link) from where i can download the rom. It's my first attempt.

dsthakur said:
plz suggest the address(download link) from where i can download the rom. It's my first attempt.
Click to expand...
Click to collapse
i suggest you to use ARHD, is the best rom for the moment, but before make sure you have the latest TWRP.
ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
Regards,
Keli

rom
dsthakur said:
let me do this if any problem occurs will let u know...
Click to expand...
Click to collapse
nothing happens after typing fastboot devices in adb command prompt. what to do next

dsthakur said:
nothing happens after typing fastboot devices in adb command prompt. what to do next
Click to expand...
Click to collapse
Have u installed the fastboot, adb drivers nd htc sync manager? All these 3 have to be installed for tge phone to be recognized. If adb devices shows nothing, then ur phone is not being recognized.

dsthakur said:
nothing happens after typing fastboot devices in adb command prompt. what to do next
Click to expand...
Click to collapse
how are you doing this?
are you using Windows 8?
please elaborate
Sent from my One using Tapatalk

rom
kamilmirza said:
how are you doing this?
are you using Windows 8?
please elaborate
Sent from my One using Tapatalk
Click to expand...
Click to collapse
after unlocking i followed this step the one in the image 1(this snapshot is from video which i followed, i didn't took mine during that), then i came to 2nd stage recovery, i don't know whether it was in the phone earlier or came after 1st process. I'm stuck at this only because i don't know anything about this, only want to start my phone in any how. have downloaded all the stuff :
1.minimal_adb_fastboot_v1.1.3_setup
2.recovery_v.0.5.img
3.openrecovery-twrp-2.6.3.4-m7ul_6.img
4.UPDATE-SuperSU-v1.91
5.Android_Revolution_HD-One_51.0
OS is windows 7 x64.

dsthakur said:
after unlocking i followed this step the one in the image 1(this snapshot is from video which i followed, i didn't took mine during that), then i came to 2nd stage recovery, i don't know whether it was in the phone earlier or came after 1st process. I'm stuck at this only because i don't know anything about this, only want to start my phone in any how. have downloaded all the stuff :
1.minimal_adb_fastboot_v1.1.3_setup
2.recovery_v.0.5.img
3.openrecovery-twrp-2.6.3.4-m7ul_6.img
4.UPDATE-SuperSU-v1.91
5.Android_Revolution_HD-One_51.0
OS is windows 7 x64.
Click to expand...
Click to collapse
please follow the steps from my first post

dsthakur said:
after unlocking i followed this step the one in the image 1(this snapshot is from video which i followed, i didn't took mine during that), then i came to 2nd stage recovery, i don't know whether it was in the phone earlier or came after 1st process. I'm stuck at this only because i don't know anything about this, only want to start my phone in any how. have downloaded all the stuff :
1.minimal_adb_fastboot_v1.1.3_setup
2.recovery_v.0.5.img
3.openrecovery-twrp-2.6.3.4-m7ul_6.img
4.UPDATE-SuperSU-v1.91
5.Android_Revolution_HD-One_51.0
OS is windows 7 x64.
Click to expand...
Click to collapse
You can try it this way:
Copy ROM zip file to c:\mini-sdk and rename it to "rom.zip"
In the same command prompt window type and confirm each command with ENTER:
mount /data
mkdir -p /data/media/0
exit
adb push rom.zip /data/media/0
Copying rom.zip to the device will take a few minutes. Wait until it's done. The output should be: xxxx KB/s (xxxxxxxxxx bytes in xxx.xxxs). Now you can flash rom.zip from inside custom recovery. Done!
http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html

ADB sideload failed

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?

bricked, stuck in recovery

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