Hi,
I've got a very odd problem:
My Nexus 5 is rooted, I flashed it many times before, the bootloader is unlocked. This morning, it crashed, and couldn't restart. No panic, I launch recovery mode and go for a wipe data / factory reset.
Two hours passed, and nothing happened, it's stuck at formatting /data.
Still no panic! Let's flash that bad boy. I used flashboot to erase all partitions, everything went fine, then flashed each one of them one by one, until system and userdata...
These two give me a "flash write failure". I think it's probably because these two are the largest, and my flash memory would be corrupted or not working at all.
My warranty is dead since one week (yay). What should I do? Maybe it's not a hardware problem and then I'm in luck? :3
EDIT: Locking back the bootloader is ineffective after rebooting the device. According to another post, this means that my eMMC chip is dead. But then why can I still write on boot, cache, bootloader and recovery?
The EMMC doesn't get "fried" per say - it's just that some sectors of it become damage beyond the capabilities of its firmware to bypass. When this happens , the firmware locks/errors out when try to write .
Edit : In your case it seems like the vital parts of it are still working - there might be a way to repartition around the damaged portions , but I'm afraid I have no idea how.
Related
Hello,
So here it how it goes:
My N5 freezes suddenly and shortly after it goes into a bootloop ( stuck at Google logo ). And from there on, the only thing I can do is just go into the bootloader.
If I go to recovery mode I can see that I get "msm_sdcc.1/by-name/misc no such directory" or something like that.
The only thing that helps make this issue dissapear is performing an oem unlock in fastboot mode, but this is not a good solution since this is the 2nd time it has happened to me in the past 3 months.
What do you guys suggest I should check/do to prevent this issue from ever happening?
Thanks!
Does the bootloader relock itself at reboot? If it does, the emmc chip is going or gone.
@audit13
The bootloader doesn't relock itself. It remains unlocked even after reboot.
I just unlock it to perform this "trick" that helps me get out of the bootloop. ( also after unlocking it, I perform a fastboot oem lock, done this both times ).
Also, don't know if it is related, when i go into recovery mode i get the android with an X or an ! (forgot which one) which is most probably due to files missing.
The screen with the dead android is normal. No need to relock the bootloader in my opinion.
Have your tried flashing a completely stock rom, including th userdata.img file to see if that solves the issue?
@audit13 Wanted to keep the stock rom with which it had come. Also doesn't an update ( from L to M for example) change the rom completely?
An ota update will move the phone to the latest of the current version (e.g. 5.0 to 5.01). The the ota will move from LP to mm.
Personally, I prefer mm.
So.. The phone did it again today, same behavior, same result ( bootloop out of nowhere ). This time I performed a complete new install of the OS ( wipe cache, factory reset + reflashed a factory image).
At this moment the phone is working as usual and now I will wait and see if the issue reoccurs (hope not).
If someone else has any other ideas an how to prevent or read some logs from the phone ( even if I performed an oem unlock ) please reply.
Hi, i have samsung galaxy tab 2 (P5100) with no root. It started to restart 5-10 seconds after android starts... (i dont have time to go the settings or to do something before restart).
I tried to clear cache and factory reset from recovery but it doesnt work. (in recovery it shows done but when i reboot system, no changes are made)...
I also tried to flash new stock room with odin but it failed every time ( i use different versions of odin, different rooms and different pits). it fails after NAND write or system.img.
Im also not able to flash new recovery... in odin it pass but when i start recovery mode there is no change...
Does someone have similar problem? Im afraid that it could be problem with motherboard or memory.
In recoveory i see this error:
# MANUAL MODE #
--Appling Multi-CSC...
Aplied the CSC-code : ORS
failed to compare '/system/csc/common/system/app/MH_10_TCS_Tablet.apk' '/system/app/MH_10_TCS_Tablet.apk' (no data available)
Thank for any help.
Your tablet may have the emmc bug, sorry but only a mother board replacement or emmc firmware update will fix it
Same problem, not yet solved.
I also have a samsung tab 2. We bought it around 2013 and started to have problems around 2015. My device started to reboot out of nowhere, infinitely, randomly. I tried to look for patterns. Couldn't find any. But i noticed something, it's stuck on it's current state. When i do things like install an app or take/delete pictures, when it restarts, everything i did would be gone and it's back to it's "current state". App that i installed? Not there. Pictures i've taken? Gone. Pictures i've deleted? It's there again. Even a hard reset won't do anything. When i do a hard reset and it reboots again, guess what, back into it's "current state" again. I've read about it on some forums, i think it's hardware related. Emmc. A notoriously bugged chip, where when you clear your cache or flash it with a new os or something like that. Boom! Brickbug. I tried sending it to the samsung dealership where i bought it. They checked it. They said the motherboard needed to be replaced, which was very expensive. I'd rather buy a new one. Now it's 2018, i'm hoping they've found an alternative to fix this tablet.
Hey all. I'm trying to salvage my mother's Samsung Galaxy Tab 2 10.1 GT-P5113.
U.S. market Tab 2 GT-P5113 with original factory ROM started intermittently bootlooping. At times would successfully boot and operate briefly but then reboot on it's own. Executed wipe process a few times but completed without success. Odin flash completes successfully on most attempts. STILL just BOOTLOOPS! Looking for a reputable service center to replace the memory.
It's been suggested that the 16 GB Tab 2 have a known faulty EMMC (MAG2GA) issue. It can happen, that your EMMC get “read only”, so you can’t perform any write actions or format anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device lifetime is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a reboot
Formating the storage doesn’t work (after reboot the old rom and apps are back)
You can flash whatever you like via Odin - it shows “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)
… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do easily at home yourself). In some bad cases you need to find someone who can replace your EMMC.
Hello everyone, first of all I want to apologize for my bad English, I'm Argentine.
I'm in a serious problem that I've been trying to solve for a year now. First of all, my cell phone is a Samsung Galaxy Ace 4 Neo, which I tried to install an unofficial rom based on CM13.
This is where everything began. When I flashed the rom, I accidentally disconnected the USB cable, causing my phone to completely crash. Determined to recover it, I had already installed the TWRP. When I proceed to want to format everything, the /system, /data and /cache partitions gave an error when being partitioned. So I stayed for 2 weeks until I visited a forum (which by the way, I do not remember what it is) that said that changing the ext4 format to exfat would allow you to format well. SERIOUS MISTAKE IS MINE WHEN TRUSTING IN THAT FORUM. By doing this I not only screwed up the phone already, but it did not even turn on. As a last resort, I used Odin to nand erase and reflash the stock rom. Surprisingly, there were no errors when reflashing, but when the phone is turned on, it remains in the boot screen. Investigating Odin's options, I realized that I can not use the re-partition option, since I get the error "Can't open the specified file. (Line: 1831)". I do not know what else to do with this phone, so my last hope is you. Please I need help!!!
Yesterday I accidentally drained my phone. I put it on charge, the next day I turned it on, but it went into boot loop. It tried to start maybe 5 times, and went into recovery. After selecting the language a strange message popped up: "kindly reminder
system error, after selecting language, please select Online update(keep data) to reover system, thanks!" (There is no such option in the recovery, only wipe, reboot and shutdown)
My 8T was with locked bootloader, last stable OTA update(13.0), no modifications.
I've had the phone discharge a couple of times before, and in all cases it was OK, just started up as normal.
But this is the first time I've had it drained on new update.
Is there any way to fix it without wiping data? I am currently in a country where there is no oneplus service center, and sending the phone to another country would be problematic for me.
I was able to dump the partitions in EDL mode, but I can't flash them. Can I use the MSM tool to simply update the phone without erasing the data?
Any help would be appreciated.
penguineer said:
Yesterday I accidentally drained my phone. I put it on charge, the next day I turned it on, but it went into boot loop. It tried to start maybe 5 times, and went into recovery. After selecting the language a strange message popped up: "kindly reminder
system error, after selecting language, please select Online update(keep data) to reover system, thanks!" (There is no such option in the recovery, only wipe, reboot and shutdown)
My 8T was with locked bootloader, last stable OTA update(13.0), no modifications.
I've had the phone discharge a couple of times before, and in all cases it was OK, just started up as normal.
But this is the first time I've had it drained on new update.
Is there any way to fix it without wiping data? I am currently in a country where there is no oneplus service center, and sending the phone to another country would be problematic for me.
I was able to dump the partitions in EDL mode, but I can't flash them. Can I use the MSM tool to simply update the phone without erasing the data?
Any help would be appreciated.
Click to expand...
Click to collapse
Try changing boot slot with
fastboot --set-active=other
TheNewHEROBRINE said:
Try changing boot slot with
fastboot --set-active=other
Click to expand...
Click to collapse
Hi! Unfortunately I have already tried this, switching slots is impossible with the bootloader locked...
After long-long research i think there is no way to fix that properly.
Now, i dumping whole phone (painful process, freed 260GB of space on my PC...) and after unlocking will try flashing userdata back.
penguineer said:
After long-long research i think there is no way to fix that properly.
Now, i dumping whole phone (painful process, freed 260GB of space on my PC...) and after unlocking will try flashing userdata back.
Click to expand...
Click to collapse
I don't think it will work. Userdata is encrypted and the key changes everytime you factory reset (although I don't exactly know what counts as a factory reset).
TheNewHEROBRINE said:
I don't think it will work. Userdata is encrypted and the key changes everytime you factory reset (although I don't exactly know what counts as a factory reset).
Click to expand...
Click to collapse
Yea, i heard about that, but i have no choice.