Hey guys,
after my phone yesterday crashed it never went to boot fully again. I was using my phone normally, when suddenly after a crash my phone rebooted to TWRP and I got the message "Failed to mount '/persist' (Invalid argument) " . So yeah I was ****ed, I didn't have any what to do and actually I couldn't do much. Reflashing over fastboot didn't work out, so flashing over twrp did the thing. I pushed the persist.img on my phone and overwrote it with a dd command and hoped everythng worked. So I rebooted and suddenly my phone doesn't get detected properly by fastboot and adb, sometimes connection established and then breaks. The second thing I noticed that my data partition is corrupt. I can delete what I want, after a reboot everything is back at the old state, I even can't repair the partition.
I actually have the feeling it is the fault of the /persist/ partition and things that have gone might wrong. I am currently on holiday and only have a macbook, a cable and my phone with me.
If anyone had that issue too and knows how to fix it else than a EDL Flash, please tell me
Regards
im having the same issue too. trying fixing now
Have you tried wiping persist partition from RECOVERY or BOOTLOADER?
Edit: I would try to wipe everything and flash them back.
Related
Okay, so I am having a lot of trouble with a bootloop for seemingly no reason. I got two nexus 6'es, and i unlocked, rooted, and flashed TWRP on mine, no problem at all.
So onto my gf's, I did fastboot oem unlock, and then i went to reboot-bootloader, but i accidentally bumped the power button, which was on "Start". It launched a weird loading style screen - the green android standing up with a blue ball spinning around (NOT the stock recovery, android laying down with chest open) , and i couldn't do anything. eventually, when i hit the volume up button, it said "Formatting /data..." but it never completed.
The only thing I could do was unplug it from my computer (mac) and put it in fastboot mode again. I tried flashing all the shamu factory images, and then rebooted again. Same thing. Now, i re-locked and then unlocked the phone again. Now it's just looping at the red, blue, green and yellow circles for over ten minutes now. What the heck can i do to fix this? I can in no way get it to boot to the lock screen, but fastboot is working fine and it recognizes the device
Edit: Got into TWRP by writing it over stock recovery. Tried to factory reset in TWRP and got the following errors:
E: Unable to mount /data
Unable to mount /cache
Unable to mount /storage
Wiping the cache should fix it.
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
Okay, i wiped cache, userdata, system and everything just to be safe, am currently finishing flashing the rest of the factory images, waiting on system. I'll let you know
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
./fastboot erase cache did not work still looping the four colored circles
joshua.justice said:
Wiping the cache should fix it.
Click to expand...
Click to collapse
Got this when trying to Factory reset in TWRP Got into TWRP by writing it over stock recovery.
E: Unable to mount /data
Unable to mount /cache
Unable to mount /storage
I was trying to take picture but suddenly my phone restarted. Then after few sec it was not booting up. It was giving me blank screen, no boot animation was coming up. So now what should I do? I try to wipe/factory reset the phone but still phone was not booting up. It was still stuck on blank screen. Please help?
Device: nexus 4
I got stuck in a boot loop also. I had to reflash the factory image. See this link here. It's the best way to do it just follow the instructions you should be fine. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Try to flash the unencrypted boot image, mine did the same thing when in first flashed TWRP to it and it. Then reflash the stock image and wipe the phone.
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
Hello guys. I have a GT-I9305 phone, bought in december 2012.
Software history: official 4.1.1 (for sim unlocking) --> official 4.1.2 --> amcha rom kk (tw 4.4.4).
Kernel history: stock --> stock --> agni
Everything was working fine until a few days ago. My battery started acting up, my screen sometimes would show lines of pixels of different luminosity and my phone would not connect to a mobile network. After plugging the phone into a socket, everything worked just fine, so i assumed it was the battery. Yesterday i had my phone on me, but unfortunately not my external battery. The phone started acting up, then it suddenly rebooted twice. First time it rebooted into os, while second time, it got stuck into a bootloop. I assumed it was just a battery problem so i removed the battery and when i got home i fully charged it. I tried starting the phone, but the bootloop was still there. I entered the recovery and tried flashing the "agni reset oc uv on boot fail" file, which was located in the internal memory. To my surprise, the phone was unable to mount /sdcard(internal memory), nor /data. I started documenting on the internet and found out that people who had this problem couldn't mount /efs as well, but i could.
While i was on 4.1.2, i read about the "Sudden death" syndrome which meant an eMMC failure. However, there was an app on play store that would tell you if your phone is affected by the bug, and it told me that my phone is safe (that was 2 or 3 years ago).
In ODIN, i can flash recoveries, however when i try to flash a full software package (one that always worked on my phone before), iu usually gets stuck on Get PIT for mapping, SetupConnection, or SYSTEM flash. I found a .pit on xda (m3xx_i9305.pit), which i assumed was the right one for the phone. However, when i try flashing the .pit, the process always fails with the "Re-partition operation failed." message.
Is it really possible that my eMMC is busted? Also, i have seen a thread for i9300 with an emergency recovery firmware. It included everything from pit to csc. Could somebody provide the files needed for I9305?
Thanks in advance.
UPDATE: USING TWRP i found out the damage was extended to SYSTEM, CACHE and TOMBSTONES PARTITION AS WELL.
WIPING USING make_ext4fs FUNCTION MADE MY PARTITIONS USABLE AGAIN ( all but TOMBSTONES). NOW I NEED SOMEONE WHO KNOWS HOW I CAN USE THE make_ext4fs function TO FORMAT TOMBSTONES PARTITION AGAIN. SOMEBODY PLEASE PROVIDE ME WITH THE NEEDED DATA. THE LOG IN TWRP says: Failed to mount '/tombstones' (invalid argument)
lyoddxd said:
Hello guys. I have a GT-I9305 phone, bought in december 2012...
Click to expand...
Click to collapse
Did you find any fix?
I too have an S3 i9505 that bootloops.
Getting the "unable to mount tombstones" when flashing or wiping.
Wunder_luftmjuk said:
Did you find any fix?
I too have an S3 i9505 that bootloops.
Getting the "unable to mount tombstones" when flashing or wiping.
Click to expand...
Click to collapse
No luck. I ended up swapping the motherboard. Sorry for the late response.
So my phone was in charger last night and when I woke up, the phone was stuck in HTC logo splash screen. I was curios to see what happened so I tried to force restart but it didn't help. The next thing I did was to enter the recovery to see if there was any problem there. What I noticed was that my sdcard was showing no data on it, so I connected it to PC and mount the sdcard, the sdcard size was suggesting that there should be data on it but there was nothing inside when I tried to open the folder. This was the first time this issue was happening to me.
So the next best thing that I had in mind was to factory reset the phone in TWRP and reinstall the ROM (Xenon HD) and then GApps. Well everything was fine and the ROM booted but since in the latest update of the ROM, root was not present, I went to recovery and installed Magisk 14.0 and then restarted it. After the restart, I notice that the phone boot loops in the ROM splash screen. So I gave it another try to reset my phone but this time only formatting the system like usual way of installing ROM. This is where the issue happened.
Every time I tried to wipe or install anything, at the first and and the end of the log, it states that "Failed to mount '/devlog' (invalid argument)". I thought it was normal and I proceeded with reinstalling the ROM but it won't boot and gets stuck in boot loop. I tried to search for this specific error but in every site, failing of mounting data or system or cache or all of them together with devlog was mentioned but not devlog by itself. I tried many ways suggested in the forums like:
Installing newer version of TWRP
Formatting the partitions to ext2 then reformat to ext4
but non helped.
I really appreciate if anyone could help me figure out how to solve this issue I'm facing. My phone is HTC M7 GSM, S-OFF and the latest GPE firmware is installed.
Thank you
I reflashed my firmware since, when I did getvar, it was showing blank version-main. This solved the error in the TWRP ( /devlog) BUT every time I try to install any ROM, after installation, it shows the ROM splash screen but then it boots loops forever. I tried many ROMS from Lolipop to Noughat all having the same problem. The other thing I forgot to mention after this issue happened there is now a black stagger line under the HTC logo whenever the phone boots. This was not there before and it only happens in that stage of booting.
I appreciate any help
Hi, I did some mistakes and ended in an state where neither the LOS Recovery nor TWRP can write to the data partition. I was again playing around with TWRP and LOS and at some point the internal storage didn't got decrypted anymore. No promt for the pattern and then no access to to the /sdcard. Flashing LOS showed no error, but results in an endless booting, till the phone switches back to the other slot.
After that I tried factory resets, with TWRP, LOS Recovery and fastboot. Some factory resets aboarded with an error message that data cant be mounted. Others worked. But data seams still to be unaccessible.
I gave up for today, but maybe someone can help me or has any clue. Any way to fix that stupid mistake? I also tried to flash stock rom but no success. But I was also not sure how to do this with fastboot. Whats the correct way to flashing stock rom back?
Thanks!
chrisrevoltes said:
Hi, I did some mistakes and ended in an state where neither the LOS Recovery nor TWRP can write to the data partition. I was again playing around with TWRP and LOS and at some point the internal storage didn't got decrypted anymore. No promt for the pattern and then no access to to the /sdcard. Flashing LOS showed no error, but results in an endless booting, till the phone switches back to the other slot.
After that I tried factory resets, with TWRP, LOS Recovery and fastboot. Some factory resets aboarded with an error message that data cant be mounted. Others worked. But data seams still to be unaccessible.
I gave up for today, but maybe someone can help me or has any clue. Any way to fix that stupid mistake? I also tried to flash stock rom but no success. But I was also not sure how to do this with fastboot. Whats the correct way to flashing stock rom back?
Thanks!
Click to expand...
Click to collapse
Hi Chris,I felt sorry for you.
There's no such thing as stupid mistake, simply because clever mistake doesn't exist. Dont be too hard on yourself, take it easy for today. Try again later, tomorow, whenever you are ready.
In the other thread, I've kindof read your screenshots' error messages, some of which i have never seen before while using TWRP. Do you mind sharing by telling us more about the mistake that you mentioned, what you did prior to encountering tht error message in TWRP? Believe that will also be helpful for other XDA members in trying to understand the root cause for your situation better.
Regards.
Was thinking maybe i would try tis...
fastboot boot twrp-3.6.1.img
Inside TWRP,
Advanced > Terminal, type
getprop | grep lock
as well as,
getprop | grep crypt
take a photo of the results and post it here.