bricked, stuck in recovery - X 2014 Q&A, Help & Troubleshooting

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

Related

[boot.img] obsolete please lock

Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit​
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.​
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.​
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?

[RECOVERY]ClockworkMod Touch v6.0.3.4

USB OTG Info:
USB OTG will show up as external_sd. If external_sd is not mounting, reboot recovery. You must enter recovery with usb already inserted.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Uncheck fastboot in the rom in power options
Turn phone completely off
Boot into HBOOT>Fastboot
Inside of fastboot. Erase cache. Use command "fastboot erase cache"
Use command "fastboot flash recovery recovery.img"
Root:
To gain root on stock rom. Flash recovery in fastboot then flash this inside of recovery. There are two root programs. Superuser and SuperSU. Both are listed.
Superuser - http://download.clockworkmod.com/superuser/superuser.zip
OR
SuperSU - http://download.chainfire.eu/supersu
Downloads:
http://goo.im/devs/Flyhalf205/MYSTUL/Recovery//recovery-clockwork-6.0.3.4-mystul.img
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Touch version is a test. Not sure if it will work properly but the classic version should be fully working. Let me know of any problems.
Flyhalf205 said:
Touch version is a test. Not sure if it will work properly but the classic version should be fully working. Let me know of any problems.
Click to expand...
Click to collapse
At least on my device, the touch recovery does *not* work, but the classic recovery *does*. Cheers!
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
One more thing to note: mounting the internal storage/sdcard does not seem to work either.
nuclear_eclipse said:
At least on my device, the touch recovery does *not* work, but the classic recovery *does*. Cheers!
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
One more thing to note: mounting the internal storage/sdcard does not seem to work either.
Click to expand...
Click to collapse
I'll take down the Touch and get a test build out....Will never work mounting the storage The internal sdcard is actually located in /data/media. It can not be mounted as storage. The only way is to use ADB commands.
Flyhalf205 said:
I'll take down the Touch and get a test build out....Will never work mounting the storage
Click to expand...
Click to collapse
That's quite a shame then. Flashing from /sdcard is by far easier to manage than using adb sideload.... :'(
nuclear_eclipse said:
That's quite a shame then. Flashing from /sdcard is by far easier to manage than using adb sideload.... :'(
Click to expand...
Click to collapse
Adb sideload or adb push to the sdcard.
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Adb sideload or adb push to the sdcard.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I tried adb pushing to /sdcard while running the recovery image, but it still refused to flash from there because it would fail trying to mount /sdcard. adb sideload was the only method that actually worked. Unless I'm missing something...
nuclear_eclipse said:
I tried adb pushing to /sdcard while running the recovery image, but it still refused to flash from there because it would fail trying to mount /sdcard. adb sideload was the only method that actually worked. Unless I'm missing something...
Click to expand...
Click to collapse
Not sure. Newer HTC phones are strange in the recovery. You mind testing TWRP?
Sent from my ADR6425LVW using Tapatalk 2
Sure, I'll test it shortly.
nuclear_eclipse said:
Sure, I'll test it shortly.
Click to expand...
Click to collapse
So, were you able to successfully root the First as well? Or was that back-and-forth about adb loading/side-loading about root? I tried re-reading the posts, but my newb-translator is on the fritz.
lordlittlebrooks said:
So, were you able to successfully root the First as well? Or was that back-and-forth about adb loading/side-loading about root? I tried re-reading the posts, but my newb-translator is on the fritz.
Click to expand...
Click to collapse
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
nuclear_eclipse said:
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
Click to expand...
Click to collapse
Thanks for spelling that out. Beers headed for you and flyhalf. Can't wait to get home and root my First!
lordlittlebrooks said:
Thanks for spelling that out. Beers headed for you and flyhalf. Can't wait to get home and root my First!
Click to expand...
Click to collapse
Thanks Glad everything is working out. Uploading a new TWRP build if anyone likes that better.
I've added a few extra features into the classic version of CWM. Power off option in the menu and reboot to bootloader in advance menu. Regular CWM doesn't have those
nuclear_eclipse said:
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
Click to expand...
Click to collapse
Is it not possible to just put zip on sdcard and choose install zip from sdcard?
Sent from my HTC first
phositadc said:
Is it not possible to just put zip on sdcard and choose install zip from sdcard?
Sent from my HTC first
Click to expand...
Click to collapse
Since the recovery currently can't mount the sdcard partition, any attempt to flash from sdcard fails. The only method that works afaik is the option to flash via sideload, which requires the phone to be attached to a PC running adb. I'm not certain, but it sounds like this would also prevent the CyanogenMod built-in update mechanism to fail as well...
nuclear_eclipse said:
Since the recovery currently can't mount the sdcard partition, any attempt to flash from sdcard fails. The only method that works afaik is the option to flash via sideload, which requires the phone to be attached to a PC running adb. I'm not certain, but it sounds like this would also prevent the CyanogenMod built-in update mechanism to fail as well...
Click to expand...
Click to collapse
Can you see the folders on the sdcard when you go to install zip from sdcard?
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Can you see the folders on the sdcard when you go to install zip from sdcard?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
No.
nuclear_eclipse said:
No.
Click to expand...
Click to collapse
Okay. I'll need to look over my configs again. New build of twrp graphics should be fixed. See if you can see sdcard on that.
EDIT: I think I see what I did wrong in my config file. Building a new build.
Sent from my ADR6425LVW using Tapatalk 2
New build of CWM classic is up. Internal storage should work.
Flyhalf205 said:
New build of CWM classic is up. Internal storage should work.
Click to expand...
Click to collapse
Internal storage worked like a charm! Thanks again FlyHalf!

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

Xiaomi.eu Rom & Encrytion

Hi,
is anybody able to get encryption working on MI8 under xiaomi.eu Rom?
I tried several times with "old" Android O and new Android P Roms from Xiaomi.eu, but after "encryption" my data partition was useless and I've to format my phone completely.
I'm on the newest 'unofficial' recovery-TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150.zip and on xiaomi.eu 8.9.20.
Thanks
hi!
you need to edit vendor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
interesting... next time i've to do a clean flash, 'll try to encrypt the device. Hope it works.
t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
Hi t0mas,
I don't have ventor on the phone but I've found vendor, can you confirm whether it was a typo or not?
As for the file itselft, I found a resemblence named fstab.qcom in /vendor/etc/.
Fyi I'm on Mi 8 8.9.24 Xiaomi.eu ROM. In order to search for the file mentioned in your post, I went through TWRP and mounted Data, Cache, System, Vendor and Persist.
Thanks for your assistance
Hi
Does it work this way?
Gunshin82 said:
Hi t0mas,
I don't have ventor on the phone but I've found vendor, can you confirm whether it was a typo or not?
As for the file itselft, I found a resemblence named fstab.qcom in /vendor/etc/.
Fyi I'm on Mi 8 8.9.24 Xiaomi.eu ROM. In order to search for the file mentioned in your post, I went through TWRP and mounted Data, Cache, System, Vendor and Persist.
Thanks for your assistance
Click to expand...
Click to collapse
oh sorry about that, of course it is a typo. i ment /vendor/etc/fstab.qcom
edit:also roccected my original post to avoid confusion
t0mas_ said:
oh sorry about that, of course it is a typo. i ment /vendor/etc/fstab.qcom
edit:also roccected my original post to avoid confusion
Click to expand...
Click to collapse
SpiderSGS6 said:
Hi
Does it work this way?
Click to expand...
Click to collapse
Thanks, I'll give it a try and let you know if everything worked out fine.
---------- Post added at 01:32 PM ---------- Previous post was at 12:51 PM ----------
t0mas_ said:
hi!
you need to edit vendor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
So in TWRP, I've renamed the fstab.qcom to old_fstab.qcom_old and copied the modified file to /vendor/etc and did a data wipe. I've rebooted the phone to system but it goes to TWRP splash screen and stays there. If I reboot the phone again, it just reboots to TWRP splash screen so my phone is pretty much stuck.
did you set correct permissions? another thing I did is flash magisk. other than that it should work as far as I know...
t0mas_ said:
did you set correct permissions? another thing I did is flash magisk. other than that it should work as far as I know...
Click to expand...
Click to collapse
My phone isn't rooted.
Right now, I can't do anything, even tried to connect it via adb but it doesn't list when I type the command adb devices
Gunshin82 said:
My phone isn't rooted.
Right now, I can't do anything, even tried to connect it via adb but it doesn't list when I type the command adb devices
Click to expand...
Click to collapse
and you did format userdata?
try starting with that. format, not wipe. you have to type in "yes" to confirm. internal sd will be wiped.
flash rom again. adb pull the file, edit it, insert it it attached zip and flash that. download latest magisk and flash that. if that doesnt work, i have no idea, sorry
I can't do any of that because the phone doesn't go in the TWRP menus, it stays at the splash screen.
I've managed to access the phone via adb but I can't access /vendor/etc/. I'm trying to put back the original file in place but when I do adb shell ls /vendor/, the only thing I see is compatibility_matrix.xml, lib64 and manifest.xml.
I'm also looking at the option of flashing the vendor partition with an image file but I can't seem to find the chinese ROM for v8.9.24
---------- Post added at 03:21 PM ---------- Previous post was at 03:07 PM ----------
t0mas_ said:
and you did format userdata?
try starting with that. format, not wipe. you have to type in "yes" to confirm. internal sd will be wiped.
flash rom again. adb pull the file, edit it, insert it it attached zip and flash that. download latest magisk and flash that. if that doesnt work, i have no idea, sorry
Click to expand...
Click to collapse
I can't because it doesn't go into the TWRP menu, I'm stuck at the blue splash screen.
I've managed to connect to the phone via adb but can't seem to access /vendor/etc/. When I do adb shell ls /vendor/ the only thing I see are compatibility_matrix.xml, lib64 and manifest.xml
**double post, sorry for that, I didn't see that my post went to the second page**
Gunshin82 said:
I can't do any of that because the phone doesn't go in the TWRP menus, it stays at the splash screen.
I've managed to access the phone via adb but I can't access /vendor/etc/. I'm trying to put back the original file in place but when I do adb shell ls /vendor/, the only thing I see is compatibility_matrix.xml, lib64 and manifest.xml.
I'm also looking at the option of flashing the vendor partition with an image file but I can't seem to find the chinese ROM for v8.9.24
Click to expand...
Click to collapse
now you lost me a bit. twrp splash or xiaomi splash screen?
if twrp, you are accessing twrp system from adb, which is separate from phone. you can try to boot in fastboot and format cache. still you did you format or wipe data before that happened? that is important.
edit: you can also format userdata from fastboot
t0mas_ said:
now you lost me a bit. twrp splash or xiaomi splash screen?
if twrp, you are accessing twrp system from adb, which is separate from phone. you can try to boot in fastboot and format cache. still you did you format or wipe data before that happened? that is important.
edit: you can also format userdata from fastboot
Click to expand...
Click to collapse
Yes, TWRP and that's where I'm accessing adb.
Not sure how to format cache in fastboot, I'll look it up
Here are the steps that I did:
1-Copy the file fstab.qcom
2-Modify the copy
3-Boot in TWRP
4-Renamed original fstab.qcom in /vendor/etc to old_fstab.qcom_old
5-Copied the modified fstab.qcom file to /vendor/etc
6-Wipe Data
7-Reboot to system
Since then, I can only reboot to TWRP splash screen or fastboot
Gunshin82 said:
Yes, TWRP and that's where I'm accessing adb.
Not sure how to format cache in fastboot, I'll look it up
Here are the steps that I did:
1-Copy the file fstab.qcom
2-Modify the copy
3-Boot in TWRP
4-Renamed original fstab.qcom in /vendor/etc to old_fstab.qcom_old
5-Copied the modified fstab.qcom file to /vendor/etc
6-Wipe Data
7-Reboot to system
Since then, I can only reboot to TWRP splash screen or fastboot
Click to expand...
Click to collapse
as far as i can tell, you did 2 things wrong
1 is you didnt format data
2 didnt set permissions
maybe 3 that backup file.
do this
fastboot format cache
try to reboot into twrp, be sure it doesnt get to booting into system
if this works, backup your sd and format userdata
if that doesnt work, boot into bootloader again
format cache again just to be shure
fastboot format userdata
this should get you to twrp. there you can flash eu again and try to boot. as far as i know eu contains vendor, so you should be fine.
if this doesnt work, the next thing i would try is to fastboot flash stock rom. be sure not to lock bootloader! in this case you might end up with a hard brick.
I'm editing my answer because it crossed your response.
So I'm guessing that Wipe Data isn't the same as format data... As for the permissions, I don't see anything regarding this, can you give me more details?
So I did a format cache and then rebooted and went directly to TWRP but it remains on the splash screen so can't access the menu.
Next step, I'll try to format the userdata as suggested and flash eu rom
maybe reflashing twrp would also help
t0mas_ said:
maybe reflashing twrp would also help
Click to expand...
Click to collapse
I'm able to access the TWRP menu. Right now I'm copying the ROM from Xiaomi.eu. I tried sideloading it but it couldn't read the file for some reason. Transfer just finish, I'll flash the rom via TWRP and get back to you after. Thanks for you help on this!!
Gunshin82 said:
I'm able to access the TWRP menu. Right now I'm copying the ROM from Xiaomi.eu. I tried sideloading it but it couldn't read the file for some reason. Transfer just finish, I'll flash the rom via TWRP and get back to you after. Thanks for you help on this!!
Click to expand...
Click to collapse
no problem, im glad you got it working.
Ok so ROM installation is done and I've pulled the fstab.qcom from vendor/etc and it's back with the encryptable variable. Phone reboots in system without any problems, just need to reconfigure everything, good thing I backed up.
I'll still need to encrypt the phone. You've mentioned the steps that I did wrong. Could we go through the proper steps for this?
Sent from my MI 8 using Tapatalk
Gunshin82 said:
Ok so ROM installation is done and I've pulled the fstab.qcom from vendor/etc and it's back with the encryptable variable. Phone reboots in system without any problems, just need to reconfigure everything, good thing I backed up.
I'll still need to encrypt the phone. You've mentioned the steps that I did wrong. Could we go through the proper steps for this?
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
dont restore the phone yet
edit file
put it in the zip i posted on prevoius page
go in recovery
format userdata->confirm with typing in yes
flash zip
i allways flashed magisk also, not sure if this is necesarry
if you just flash without formatting, you will probably break stuff again

Question I might have bricked my phone, I need help

I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.
Try putting the stock ROM on a SD card or usb (if you have a dongle).
georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem
Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?
Plus, where did you get the ArrowOS image? There are no builds, official or not.
georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card?try click on the Install image and change to install zip
can you sideload?
I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now
you should format data and put the arrow build in it, maybe it will work
J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.
raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.
georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?

Categories

Resources