Database Develop

Bricked device

Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.

Leader0fr4tz said:
Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Click to expand...
Click to collapse
adb root; adb remount

Does your phone get recognized by your pc?
Mine went black a few days ago and i cant do anything.

LuK1337 said:
adb root; adb remount
Click to expand...
Click to collapse
Hi LuK1337
Firstly thanks for the help.
adb root returns a message saying adb already has root access.
asb remount only remounts the /system partition (unless im using it incorrectly).
So far I have well and truly wiped every partition of this device excluding the /data partition which returns a message saying partition is read-only

So I have now officially proved that this is a hardware issue at least for me, look here for my findings:
http://forum.xda-developers.com/moto-g-2014/help/battery-drained-encrypted-device-pinned-t3079871/page2
Short version I've used every available software method including 'Fastboot Erase all' which has no effect.
So would anyone be able to help build a usb jig or finding a hardware way to fix this ? my device has been opened so I would be able to provide high res pictures of the motherboard to anyone who needs it, will also upload when my 10 post count has been reached

Solved: Dead battery stuck in fastboot mode unable to flash any image. Works for all.
Same thing happened to me.
Nothing to do with the hardware.
Steps to Follow:
1) Open fastboot mode in your phone.
2)Connect to your pc and open cmd in platform-tools folder.
3)Place the twrp.img file in platform tools.
4)In cmd, type : fastboot boot twrp.img (Very Important Command)
Now your phone will boot to recovery mode i.e. TWRP and the connect it to charger. It will charge slowly.
Now you can flash anything using ADB Sideload.
(If found helpful, hit the thanks button )

Bricked phone, what can I do?

Hi there. My cousin's phone stopped working some weeks ago. He tried to wipe everything via TWRP and installing different ROMs but no ROM seems to work. Now, when he does a complete wipe, he gets the error "E:Unable to wipe '/sdcard1' -- unknown file system 'auto'" and "Unable to mount storage". Also, now everytime he tries to copy a ROM to the TWRP folder (the only folder which appears on his MacBook or his friend's PC) it stops at 16k and he can't copy it.
What can he do to fix this? Nothing seems to work and a guy at a service center said it was a disk error and that there was no hope for the phone.
Here's a screenshot of it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!

Uhm... Why don't you remove the faulty micro SD from the phone?
This doesn't look like a bricked phone at all - "storage" and "sdcard1" refer to external storage.
Remove the phones's cover and remove the SD card (do NOT go beyond step 2, FFS). Then you can try to run some diagnostics or format it on your working phone, tablet, MAC or PC or you can buy a new one - they are quite cheap.
Then add a proper ROM (and proper GApps) on the card and stick it back in. Moto G 2014 comes in two variants - make sure your cousin's device is an actual Titan - chances are it is a Thea, if you're in Europe; that's why the TWRP doesn't want to install it. Choose one from here.
Remember you have to delete everything on the internal card through the recovery utility I see in your image before flashing a new ROM - do NOT wipe the SD Card; it stores your installation files: the properly chosen ROM and GApps you add after you format it through a different device.
If it works, make sure you do NOT format it as adopted/internal storage when/if asked by the installation wizard at first run, once the flashing is complete. This is probably why the phone got in this state in the first place.

Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!

Framboesa96 said:
Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!
Click to expand...
Click to collapse
Why don't you try reflashing the stock rom..Once I encountered a similar problem and reflashing the stock rom solved it

[SOLVED] Stuck on stock recovery, adb/fastboot/flash from sd wont work

Solved: This thread may be deleted, sry for bothering you.
I wasnt aware of how to get into fastboot from the stock recovery: Turn off device (Hold down VOLUME UP, VOLUME DOWN and POWER at the same time for a few seconds), remove SD card (in case there's a ZIP that will get auto executed) and boot into bootloader (VOLUME DOWN and POWER for a few seconds).
Old post:
Hello Community!
I'm stuck on the stock recovery with neither fastboot nor adb recognising my device and flashing from SD card giving me "check cid failed, Invalid operation".
How did it come to this:
Tried out Costum ROMs (Linage & Carbon),
restored old backup with TWRP
thought I'd wanna see the stock ROM,
flashed boot image and stock recovery according to this guide
thought it would be a good idea to reboot
regret the last part cause stuck on recovery.
What does it look like atm:
When I turn on the phone, it will stay in the booting screen for some time (white background, "HTC powered by android"), go black, go booting screen again and then go stock recovery (black background, red rectangle with exclamation mark inside)
So I hold VOLUME UP and press POWER, which gets me here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried them all, check cid failed, invalid operation.
When connecting to PC, Windows gives me the devices recognition sound, but adb and fastboot act as if no connection:
What else did I try:
Uninstalled HTC drivers, reboot, install HTC sync manager, uninstall sync manager but leave drivers.
tried different ports and cables as well as SD cards
I don't get why it won't flash from SD card. I tried with different TWRPs in zip, rar and img format, named them 0P8BIMG.* and 0P6BIMG.*
When there's no SD card inside it gives me an error, so it does recognize the SD card.
Last but not least about the bootloader: I locked and unlocked the bootloader shortly before this all happened, so I guess the bootloader is unlocked. However after all I'm merely a noob in all of this, so what do I know.
Any unbricking suggestions?

HELP: After updating to android 10

After the update, this message appears after restarting, updating by OTA, not boot
how to fix this?
translate:It is not possible to load the android system. Your data may be corrupted. If you continue to receive this message, it may be necessary to perform a reset to the original configuration and clear all user data stored on this device.
Try again OR reset to original configuration
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm sorry for what has happened to your phone. It's probably caused by some corrupted files while uploading or the file integrity has been jeopardized since something similar happened to me while I was trying to unlock the boot loader without wiping the phone. I'd say there's not a chance to get your datas back if you've got a locked boot loader but if you're unlocked you might wanna try pulling important files from the storage using fastboot or TWRP. But at the end a wipe is necessary for phone to function correctly again.
Have a nice day.

A quick solution might work.
Solution steps:
0. Get the adb/fastboot tools from Google
1. Mobile Go to fastboot
2. use ‘fastboot getvar current-slot’ to determine what slot you are on, which is damaged. You will get either a or b
3. use ‘fastboot --set-active=b’ or ‘fastboot --set-active=a’ for setting active slot to another. Hence, set it to b if you got a from step 2.
4. Restart.
The possible reason and why doing this:
1. If ota is working, the original system partition is untouched for sure, since ota check system partition during the process.
2. The ota extract rom to another slot, and set the active slot to another after reboot.
From what I saw here, there is some problems between the original data partition and new system partition, but they might Woking with the old one.
Sent from my Mi A2 using Tapatalk

Fastboot can switch slots for fully unlocked phone only.
If phone is not unlocked, options are:
- make reset and loose data, or,
- if data is to be preserved - remove SIM, plug external power, and continue retrying reboots (bootloader of AndroidOne phone with A/B slots is supposed to determine after numerous attempts that current slot does not contain bootable OS and automatically switch to previously active slot).

Aerobatic said:
Fastboot can switch slots for fully unlocked phone only.
If phone is not unlocked, options are:
- make reset and loose data, or,
- if data is to be preserved - remove SIM, plug external power, and continue retrying reboots (bootloader of AndroidOne phone with A/B slots is supposed to determine after numerous attempts that current slot does not contain bootable OS and automatically switch to previously active slot).
Click to expand...
Click to collapse
Tbh from several research, I can't find evidences that suggest swapping slot require unlocked bootloader.
Since we normally unlock bootloader at the very beginning.
Either way worth trying.
Sent from my Mi A2 using Tapatalk

As a matter of fact, "fastboot set_active b" in full stock phone state returns: FAILED (remote: 'Slot Change is not allowed in Lock State').
So, for those who did not unlock MiA2 beforehand, the only hope to save data in OTA-generated bootloop state is to rely on AndroidOne "A/B (Seamless) System Updates" and keep trying to boot.
https://source.android.com/devices/tech/ota/ab
https://source.android.com/devices/tech/ota/ab/ab_implement#bootcontrol

Need help flasing Paranoid Android - All TWRP'd up

Hi all! This is my first attempt to flash a custom rom and I'm stumbling. Summary below:
DEVICE AND SYSTEM:
Xiaomi Mi 6X
Running MIUI 11.0.6.0(PDCCNXM) (based on Android 9)
Device bought in China in 2018, not used until now, only updated through Xiaomi OTA.
Mi Unlock status - Unlocked
Developer options unlocked
USB debugging - activated
Phone not rooted.
Phone has no lock screen password set.
FILES TO FLASH:
1. dm-verity anti-rollback flash:
no-verity-opt-encrypt-6.0.zip
2. Paranoid Android custom ROM:
pa-quartz-5-wayne-20200924.zip
METHOD
I'm using Google pltaform-tools (https://developer.android.com/studio/releases/platform-tools) + TWRP files (https://twrp.me/xiaomi/xiaomimi6x.html) and command prompts in adb and fastboot.
WHAT HAS WORKED SO FAR
adb devices OK - cmd shows hexa key
adb reboot bootloader OK - phone enters fastboot
fastboot flash recovery twrp.img OK - cmd shows Finished. Total time: 1.504s
fastboot reboot (holding recovery key combo to avoid entering automatic MIUI recovery) OK - TWRP loads
Then the problems start. TWRP shows:
Mount
Decrypt Data
Enter Password
and no password in the realms of man or heaven works. by clicking cancel as a workaround several mounting problems appear:
THE ISSUE
Since TWRP can't decrypt internal storage, I can't find the zip files I copied to the phone's memory.
Googling around I found the OTG option and tried it. But as it turns out it's also impossible to mount OTG (on Mount, the option for OTG appears but clicking it does nothing)
Googling more I found out about abd sideload, but TWRP fails to start the feature (on Advanced -> ADB sideload -> select Wipe Dalvik Cache + Wipe Cache)
Also googling intensely I found that by wiping the memory (on Wipe - Format Data - write "yes") then reentering recovery it was possible for TWRP to enter a decrypted mode. after doing this no password is required but both OTG and ADB show the same problems as before (and of course the internal memory files are no longer there).
As a summary of my woes, this is what I've tested so far and the results:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Assorted tests with older versions of TWRP have exactly the same results.
After every wipe I have to set up MIUI11 again, open developer optios, allow USB debugging etc. My fingers hurt. Morale is low. My soul is leaking. Any ideas on where to go next? Is this some unfixable incompatibility between TWRP and MI? I think I've exhausted the paths I can find by just googling around like a progressively more hairless maniac noob.

TWRP sucks for mi 6X. Download this one (OrangeFox Recovery) and everything works fine.To install it extract the zip and flash the recovery.img that is there. After that reboot to recovery and if it still asks for password just ignore, go to menu, manage partitions, clik on data, click on the button that will show, then format data and type yes. This will clean every partitions (It's the only way i found to fix encryption since our device doesn't support sd cards)Then download the Rom you want to your pc and then copy to your phone storage and install it. Good Luck.