We had a Note 5 at work get messed up. I have no idea what happened to start this but the issue is that it won't boot into the OS at all. I can get into download mode and recovery only with a custom one, using TWRP. Even when I do get into recovery wipes resets won't work. Trying most get the error about data being uncountable. When you look in TWRP internal storage shows as 0 and when you look at the data partition is shows as 0. Also when in recovery it will random reboot itself. I can't fastboot as the drivers won't work with fastboot. Tried everything to flash the latest stock rom and everything else I can think of. I was going to try wiping the EFS partition but Odin gives and error failure. Running out of ideas.
Related
I want to see if I can get this resolved without running the RUU first.
Basically, I tried everything I could to get either Hatka or Borked to install. Hatka would install but not boot, and Borked would go through the install as if it worked, but never flash anything. Finally gave up, and rebooted to try and get into recovery and restore my backup, only to have it reboot after seeing the teamwin logo. Strange. Tried to "fastboot boot" an older TWRP. Same result. Clockwork? Same thing. I've had something that from memory was identical in the past, that just randomly resolved itself, but just in case anyway...
Thank you for your help!
Fixed. Figured out I could wipe partitions with fastboot.
fastboot wipe boot
fastboot wipe system
fastboot wipe data
Recovery booted fine after that.
I use TWRP 2.8.7.1(which was flashed to the phone) and now after flashing this nightly version, the recovery gets stuck on the TWRP screen and flashes every 60 seconds, but never lets me use it.
I've searched through all the forums, but can't find anyone else with this problem. I just want to flash CM12.1 Snapshot, but I can't without the recovery working.
Everytime I flash the same recovery(TWRP2.8.7.1), the bootloader gives me the error "Mismatched partition size". I've tried "Fastboot boot TWRP2.8.7.1.img, but it sits stuck on the loading TWRP screen. I've cleared the cache, but still nothing.
The only recovery that I can get to work is CWM by booting the .img from the bootloader, but that still does nothing because none of the directories will mount, so I cant flash from the recovery.
I'm waiting on motorola to send me the stock files and just reflash stock and start from scratch, but I really want to save my data.
Does anybody have any clue as to what I'm doing wrong before I reset to stock?
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
uluf said:
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
Click to expand...
Click to collapse
Nope.. didn't work. I had the 5.0 files from motorola that I flashed, and I'll update from there.
I really wish motorola would leave those files open to download instead of having to wait... sucks not having a phone, but I survived.
i have the same issue, any idea how to fix it ?
Hi, I need help with a (possibly) soft bricked phone. It boots, yet it reboot itself once it tries to read the multimedia files in the internal storage. The owner is a co-worker so I really don't know how or what could possibly trigger this behavior (a virus perhaps?). The device is not rooted, even if I set usb debugging it just keep rebooting and losing all configuration. Uninstalled apps respawn again once it reboots. I tried to flash it with many Odin versions to a proper stock rom, but when the device reboots all the files remain the same, as if nothing were ever done. I tried wiping everything from recovery mode, didn't work either. Whenever I enter recovery mode it updates some files and says it can't gain access to CSC. I'm not an expert on repairing phones so I'm already out of options, any suggestion would be appreciated.
Edit: Android version is 2.3
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Cassiusss said:
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Click to expand...
Click to collapse
Didn't work either. All files are still there after rebooting. CSC still fails to load in recovery.
I saw some people with this issue in other android devices, it seems the problem is a corrupted internal memory (nothing can be erased or written). I may just give up
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Cassiusss said:
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Click to expand...
Click to collapse
I can't install custom recoveries, it doesn't recognize external storage and not even Odin can rewrite the recovery.
If you're sure that you can't install TWRP with Odin then I don't know how you could solve your problem, sorry. :/
@Cassiusss Hey Bro,
I have been using epirex cm13 builds
but later these days, i didnt used it much as i was flashing around on my 1+3.
Now, i cant boot in recovery and bootloader, whenever i reboot to recovery or bootloader it boots back to rom.
i try adb commands and flashing recoveries through app but didnt work.
Also I tried odin flash it but as it cant boot in bootloader, how can i revert back.
I am using 12 june build Cm13.
Please help.
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Cassiusss said:
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Click to expand...
Click to collapse
I tried ur mentioned app but it again takes 1-2 secs and boots to system.
I also extracted out boot.img from cm13 and flashed it through rashr but after flashing it again booted to system.
Also tried to factory reset from phone but surprisingly it again didnt show anything and booted to system.
Can You tell me any method to HARD RESET or format its system partition so i can odin it ezily.
I think that formatting system will not bring back recovery or download mode.
What's important is to gain access to download mode (because without it you can't use Odin).
Are you sure that booting your phone while pressing "Volume down" + "Home" + "Power ON" keys is ineffective?
Maybe you'll need an USB JIG to force the download mode...
I guess your device memory is broken. Because my friend's ace3 had the same problem with you, and the service center said that the emmc had been broken. So no hope at all
So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
I had an issue where my tablet would just reboot over and over. So I tried to reset it using factory reset. This has me now in a recovery reboot loop.
Hardware:
Galaxy Tab S2 (SM-T713) - wifi only
Software:
TWRP 3.1.0.1
Lineage OS 16
What I've tried:
Wiping cache and davalik cache several times
Formatting data
adb reboot fastboot
Wiping cache, davalik cache, and system (which made TWRP report no system of course)
adb sideload of lineage OS 16 - reported success but TWRP still said no system
re-flashing the lineage OS 16 ROM from SD card (this resolved the no system issue)
Reboot to system from TWRP and adb fastboot after the system re-flash
Odin won't respond and says it can't contact the tablet (multiple usb cords tried , etc) so no luck re-flashing OEM ROM
No matter what, it goes into recovery reboot and won't try to start the system. I can't find anything else to try through searches on XDA, google, etc. Any suggestions?
Not exactly the same, but I thought I had hard bricked my T713 about 9 months ago. I was on stock at the time (not even sure what build), and a bunch of wipes and formats later I was in a TWRP loop. I couldn't even power the machine down. Even that would loop me back to TWRP. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power and volume down and spam the home button until I got to the download screen. After that I was able to get back into odin3_v3.12.5 and load the factory image. I am on LineageOS 16 official now, so I have no idea if this is of any help. I'm pretty sure the boot img came after drilling all the way into the XAR-T713XXU2BRB2_T713XAR2BRB2-20180206 file, since that is the one I eventually got to load.
Yes, I forgot to mention that symptom - it won't power down at all. Just goes back to TWRP.
I'll give that a try, thanks.
apollard said:
Yes, I forgot to mention that symptom - it won't power down at all. Just goes back to TWRP.
I'll give that a try, thanks.
Click to expand...
Click to collapse
Flashing the boot.img file did it! I was able to get in to download and use Odin to reflaah the stock ROM. Now to switch to LOS.
apollard said:
Flashing the boot.img file did it! I was able to get in to download and use Odin to reflaah the stock ROM. Now to switch to LOS.
Click to expand...
Click to collapse
I am so glad that worked for you.