Database Develop

Unable to mount /data, fastboot doesn't seem to be able to write

Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068

Are you able to pull logcat?

Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"

dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.

i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?

It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app

Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.

PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.

jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.

You can try by helping me to look for a circuit PDF from the board or trying it yourself.

I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately

Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.

any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?

gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.

I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate

we can connect through hangouts / etc.
look up for my user at gmail

Bootloop after flashing factory images

Hi everyone.
Anyone encountered this when flashing back to factory images? During normal boot, the phone will show some weird corrupted images (as attached) and reboot by itself. Is it a hardware issue?
I tried flashing different 5.1/5.11 factory images but end up with the same result.
Bootloader is ok. Able to fastboot.
Fastboot shows success for every img I flashed.
Able to boot to recovery. Able to install custom recovery (latest TWRP) and access ADB.
Have wiped cache and factory reset after every attempt.
Unable to flash custom roms for some reason. Already tried 3 custom roms. ADB sideload/install zip from custom firmware hangs. TWRP sometimes crash during flashing.
Any insight/help will be appreciated. Thanks!

It seems like a hardware issue....but....it seems like your not wiping data (internal memory) on the nexus 6, anytime u flash full factory images and your decrypted, you have to wipe your entire memory, or it will bootloop.....try fastboot format userdata and fastboot format cache....I suggest u move any files and pics to your computer before u do ...itit encrypts your phone when u flash stock images

I've wiped entire phone before flash. After flash, I also did a erase cache and full factory reset from recovery. The results is still the same.

Tried flashing Android M preview 3. Same issue encountered. The message 'Device is corrupted' error appeared also.
Tried flashing custom roms. Always got stuck at 13/14% at 'patching system image unconditionally.' Anyone can help?

Any pro can advise?

Try "fastboot format userdata" as suggested above before asking for more advice. It is not the same as a wipe.
That said, the screen looks odd and looks more like a hardware issue.

Thx. Already format userdata umpteen times as mentioned before and after every flash.

The garbled screen only appears during bootup. During bootloader mode, factory recovery mode and in twrp, the screen appears perfectly normal.

You hadn't mentioned you had formatted once until now. You have said "Have wiped cache and factory reset after every attempt." which is *NOT* a format.
If you want help, you'll have to be more accurate in your posts.
Flash stock and FORMAT userdata (not wipe, not reset).
If you have a problem still, send it for repair / return.

Well, thanks but your answer is no help. If I want to send for repair/return, I won't even ask here.
And by your first post, you instantly assumed that I did not tried format. Please don't be overbearing to assume. If this is the kind of responses I can get from this forum, forget about it.

To prevent you from further assuming, let me clarify this post: 'Thx. Already format userdata umpteen times as mentioned (BY JAMESCABLE) before and after every flash.'

Hardware failure. Good luck
For help with your FUTURE issues, please describe ALL the steps you have taken to remedy or reproduce an issue. Like you say, we cannot assume you have done something if you haven't told us. I didnt assume you hadn't formatted. I assumed your first post was accurate. If your post is not accurate, that is YOUR FAULT, not mine!!!
Also if someone asks you to do something that YOU HAVE NOT told us you have done, don't try to pretend that you had already told us and then be a smart-ass. No one likes to help a smart-ass, so try to be a more polite and accurate forum member.
Anyway, sounds like you're screwed so....

Well, thanks for the responses. But I don't think I want to hear anything else more from a smart ass parrot who only repeat's other's advice, self-assuming that I am so dumb not to try an existing solution provided and the best contribution so far from this parrot is to send the phone back to repairs.
Well, speak for yourself, smart ass. U are the one who had been assuming. And talking about politeness, you yourself isn't even polite in the very first post of yours.
If you are not sure whether any steps had been tried, please ask. I am not new to this entire flashing business and I don't need to write an article how did I troubleshoot this phone, if that's what you are looking for.
Well, I am not entirely screwed. I bought this phone for a mere US$30 just to play troubleshooting with it. So whether it gets repaired or not is not an utmost concern with me.

haha,
Whatever.

E: can't mount /system , /cache

Hello, I have an htc desire 510 cricket that became unusable. so, I attempted to factory reset it, but that did not work. So, in my quest to find an answer, I have tried many different things. I think in the process I have accidentally wiped the system and cache. Then I began to get the system and cache cannot be mounted errors. So, I followed the directions of reformatting those sections using twrp. Still they have remained unmountable. I have tried all the instructions online that I can find. However, now, I cannot load twrp. I can't even boot into twrp from fastboot. When i try recovery or factory reset in the bootloader the phone merely vibrates, blanks and then goes back to the bootloader.
anyone have any ideas how I can bring this back to life, if at all possible?
Thanks in advance for any help you may be able to give.
Dave

Another thing I just noticed
bramwell40 said:
Hello, I have an htc desire 510 cricket that became unusable. so, I attempted to factory reset it, but that did not work. So, in my quest to find an answer, I have tried many different things. I think in the process I have accidentally wiped the system and cache. Then I began to get the system and cache cannot be mounted errors. So, I followed the directions of reformatting those sections using twrp. Still they have remained unmountable. I have tried all the instructions online that I can find. However, now, I cannot load twrp. I can't even boot into twrp from fastboot. When i try recovery or factory reset in the bootloader the phone merely vibrates, blanks and then goes back to the bootloader.
anyone have any ideas how I can bring this back to life, if at all possible?
Thanks in advance for any help you may be able to give.
Dave
Click to expand...
Click to collapse
Now when I just try to start my phone normally, it automatically goes to the fastboot screen. It won't even try to boot up.

Mi A2 Bricked, Solved

Hi, I need some help with my Mi A2.
I tried to install the RR Rom and was already struggeling in the beginning to get twrp up and running, after I got twrp running Ive got, while trying to install the RR rom (yes I did wipe everything that needed to be btw) error code 1 . So I tried to just shut my phone off and retried the installation after being back in twrp. and it did sort of install, I wasnt getting any error this time but after rebooting or atleast trying to I was stuck in a bootloop. soooo, I went back into twrp and tried wiping everything except internal storage and did an factory reset. but now fastboot mode wont let me use any commands for example "fastboot boot twrp.img" it just responds with "command write failed" or something like that. and when trying to boot into the "system" I get an blackscreen with a smal text in the top left corner saying "press any key to shutdown".
I hope someone can help me I tried now for hours to get anything running.
as a side-note I am not that new to flashing roms but, I have no idea what I screwed up this time.
Thanks for anyone that tries to help!
Edit: Using MiFlash and downloading the stock room from Xiaomi worked.

Minxxe said:
Hi, I need some help with my Mi A2.
I tried to install the RR Rom and was already struggeling in the beginning to get twrp up and running, after I got twrp running Ive got, while trying to install the RR rom (yes I did wipe everything that needed to be btw) error code 1 . So I tried to just shut my phone off and retried the installation after being back in twrp. and it did sort of install, I wasnt getting any error this time but after rebooting or atleast trying to I was stuck in a bootloop. soooo, I went back into twrp and tried wiping everything except internal storage and did an factory reset. but now fastboot mode wont let me use any commands for example "fastboot boot twrp.img" it just responds with "command write failed" or something like that. and when trying to boot into the "system" I get an blackscreen with a smal text in the top left corner saying "press any key to shutdown".
I hope someone can help me I tried now for hours to get anything running.
as a side-note I am not that new to flashing roms but, I have no idea what I screwed up this time.
Thanks for anyone that tries to help!
Click to expand...
Click to collapse
Try installing Stock Rom using MiFlash

gmoura5010 said:
Try installing Stock Rom using MiFlash
Click to expand...
Click to collapse
Yea, did that yesterday and that recovered my device. Still thanks for the advice.

Question My Realme x7 max 5G stuck in recovery loop after uninstalling bloatare like glance, finshell pay, hot apps

like the title says I uninstalled the mentioned apps using adb and all of a sudden my camera stopped working so I decided for a simple restart and the device stuck in the loop ever since.
it restarts several times and open realme UI recovery and when I choose language it says " KINDLY REMINDER : system error, after select language, please select Online update(keep data) to recovery system, thanks! " .
So I did what the message said and I connect the wifi but instead of updating it says no updates found.
I also tried to wipe data but I got asked whether to retain contacts/media or format data.
I obviously tried the first one because I need the data but as expected it didn't work.
I am skeptical to clean format because I feel that I can still fix it with retaining the data.
I tried all the key combinations but only the realme UI recovery comes up . Please help me!
thank you

I don't think you'll be able to fix this without a full reflashing of the ROM using SP Tools and a format of the data partition from Recovery. You probably don't have access to full ADB now, if at all, and Fastboot won't help you recover anything. However, you should be able to rescue important files before you do this, as long as you have unlocked your bootloader.
Follow the steps here to install TWRP custom recovery. Once done, you can boot into it from fastboot by running `fastboot reboot recovery`. Once you're in TWRP, you can mount partitions so you can access them over USB from your PC.
Once you've got your important files transferred to your PC, take a full backup to be safe, then flash the stock ROM. This thread can help you do both of those things. Note that flashing the stock ROM using SP Tools will also restore the stock recovery. Once the process is done, boot right into fastboot and use it to reboot back into the stock recovery before letting it actually boot the ROM. Format your data partition (yes the whole thing). Now you can restart, and it should go through first time setup just fine.

I was going to uninstall these apps, but was too lazy. Guess lazyness is not too bad after all.

@Ricodey have you got the solution for this thing beacause i am also experiencing same issue

e_v_i_l_x_ said:
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
Click to expand...
Click to collapse
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance !

Ricodey said:
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance
Click to expand...
Click to collapse
for me the issue was like i just downgraded my device to the a.15 firmware after setting up i uninstalled the bloatware apps and some google apps which were not needed obviously and restarted my device and it got a bootloop, the issue of bootloop wasn't new to me i previoulsy had the same issue when i have downgraded to a.19 firmware. there is a simple fix, if you want to get rid of the bloatware apps now also you can use the disable command like.
(pm uninstall-user --user 0 ----package name---) this will not give any bootloop and can enjoy a part of RAM....
THIS WILL HELP
get in touch if need anything else